In the current implementation of the modemmanager 'proto', if a 'plmn' and a
'technology' is configured, the 'plmn' is set first and then second the
'technology' on a 'proto' setup.
However, this is problematic if a 'technology' has already been set in an
earlier run. It is possible, that this previously set 'technology' is not
available at the current location, as the modem remembers the setting.
To fix this, first set the technology and then the plmn.
Signed-off-by: Florian Eckert <fe@dev.tdt.de>
(cherry picked from commit
3a5aa8a387d82e0e02a67bfa96a050c2f01d6edf)
[ "$?" -ne "0" ] && return 1
}
- [ -z "${plmn}" ] || {
- echo "starting network registration with plmn '${plmn}'..."
- modemmanager_set_plmn "$device" "$interface" "$plmn" "$force_connection"
- [ "$?" -ne "0" ] && return 1
- }
-
if [ -z "${allowedmode}" ]; then
modemmanager_set_allowed_mode "$device" "$interface" "any"
else
[ "$?" -ne "0" ] && return 1
fi
+ [ -z "${plmn}" ] || {
+ echo "starting network registration with plmn '${plmn}'..."
+ modemmanager_set_plmn "$device" "$interface" "$plmn" "$force_connection"
+ [ "$?" -ne "0" ] && return 1
+ }
+
# setup connect args; APN mandatory (even if it may be empty)
echo "starting connection with apn '${apn}'..."