| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
| |
Signed-off-by: Aleksander Morgado <aleksander@aleksander.es>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
A network restart where netifd is cleanly restarted involves bringing
the network interfaces down. The 'modemmanager' protocol handler will
run a mmcli --simple-disconnect in this case, but only if there are
bearer objects found.
If the network restart happened *during* the connection attempt
procedure, while the modem is e.g. being registered in the network, no
bearer objects exist yet, and so, we would skip doing anything during
the interface teardown operation. This would lead to the original
connection attempt succeeding, so leaving the modem in ModemManager
in connected state, while the associated interface in netifd is
reported down.
Signed-off-by: Aleksander Morgado <aleksander@aleksander.es>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Added signal refresh rate option
modemmanager: update readme.md
Added description for added proto options.
Added compile option to compile --with-at-command-via-dbus for allowing
AT commands to modem without --debug flag
Changes to be committed:
modified: net/modemmanager/Config.in
modified: net/modemmanager/Makefile
modified: net/modemmanager/files/modemmanager.init
modified: net/modemmanager/files/modemmanager.proto
modified: README.md
Signed-off-by: Valtteri Holopainen <valtsu@gmail.com>
|
| |
|
|
| |
Signed-off-by: Nicholas Smith <nicholas.smith@telcoantennas.com.au>
|
| |\
| |
| | |
Authentication protocol setup in ModemManager
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
ModemManager allows specifying which are the authentication protocols
to be used during the user/password context authentication with the
peer.
This protocol update allows users to provide a new 'allowedauth'
option in the interface configuration, which is then used in two
different places:
* It is sent to ModemManager in the --simple-connect call so that
modems with a network interface can perform the authentication
using their own vendor-specific protocol.
* If the connection is done using PPP, this list of protocols is used
to configure the pppd call.
If the new 'allowedauth' option is not given, all auth protocols are
implicitly allowed.
Signed-off-by: Aleksander Morgado <aleksander@aleksander.es>
|
| |/
|
|
|
|
|
|
| |
Using the same method used by other protocol handlers like uqmi.
Fixes https://github.com/openwrt/packages/issues/11383
Signed-off-by: Aleksander Morgado <aleksander@aleksander.es>
|
| |
|
|
|
|
|
|
|
| |
Unlike other modem protocol handlers like the ones implemented by uqmi
or umbim, in the modemmanager protocol handler the 'device' option
does not specify a device node in /dev. Therefore, we shouldn't flag
the option as 'device' type (dt_type_device).
Signed-off-by: Aleksander Morgado <aleksander@aleksander.es>
|
| |
|
|
|
|
|
| |
Otherwise, if the modem is reseted, netifd will think that the device
is gone forever.
Signed-off-by: Aleksander Morgado <aleksander@aleksander.es>
|
| |
|
|
| |
Signed-off-by: Aleksander Morgado <aleksander@aleksander.es>
|
| |
|
|
|
|
|
|
|
|
|
| |
When the user requests 'any' as 'iptype', we may get either IPv4 or
IPv6 settings.
Simplify the logic by not requiring any explicit iptype before loading
the method reported by the bearer object for IPv4 and IPv6; just load
the methods right away and setup settings based on those.
Signed-off-by: Aleksander Morgado <aleksander@aleksander.es>
|
| |
|
|
| |
Signed-off-by: Aleksander Morgado <aleksander@aleksander.es>
|
| |
|
|
|
|
| |
Also, explicitly close the JSON object.
Signed-off-by: Aleksander Morgado <aleksander@aleksander.es>
|
| |
|
|
|
|
|
| |
The bearer status wasn't being loaded in key/value mode, and therefore
would always fail to load the IPv4 config method.
Signed-off-by: Aleksander Morgado <aleksander@aleksander.es>
|
|
|
Signed-off-by: Nicholas Smith <nicholas.smith@telcoantennas.com.au>
|