...
A new /run/wwan/<network-uuid>/config.json will be added for each LTE network to submit LTE configuration from nim to wwan service, including the required airplane mode state, e.g.:
| No Format |
|---|
{
“apns”"physical-addrs: [“internet”],{
“interface”: “wwan0”, # Update: interface name can be obtained from cdc-dev
“cdc-dev”: “cdc-wdm0”,
“airplane-mode”: “off”,
“probe # nim will specify one of these. With multiple LTE modems, the USB address is the most unambiguous and reliable.
“interface”: “wwan0”,
“usb”: “1:2.3”,
"pci": "0000:11:00.0",
},
“apns”: [“internet”],
“airplane-mode”: “off”,
“probe-ip”: “8.8.8.8”
} |
One thing that we still need to figure out is how to appropriately reference an LTE modem in NetworkConfig/WirelessConfig, i.e. how to go from some human readable (and persistent) “modem ID” to the corresponding CDC device path and the interface name. Until then nim will publish hard-coded wwan0 and cdc-wdm0 values. Maybe user could select the modem by IMEI number? Also, the probing IP (by which wwan service determines if the connection is working) will be hard-coded to google DNS IP but eventually it will be made configurable (i.e. making all these configurable is out-of-scope for this proposal)Note: interface/usb/pci will be obtained by nim from AssignableAdapters based on the PhyLabel of NetworkPortConfig.
Next a new /run/wwan/<network-uuid>/status.json with modem state data will be published for each LTE network by wwan service for zedagent to read. Status file will contain MD5 checksum of the last applied revision of config.json. With this, EVE will know when there are no more pending configuration changes, so that it is ready to publish radio state up to the application.
...