modemmanager: swap plmn and technology set command in the proto

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>
This commit is contained in:
Florian Eckert 2024-11-05 08:37:02 +01:00 committed by Florian Eckert
parent 8682084e34
commit 3a5aa8a387
1 changed files with 6 additions and 6 deletions

View File

@ -644,12 +644,6 @@ proto_modemmanager_setup() {
[ "$?" -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
@ -679,6 +673,12 @@ proto_modemmanager_setup() {
[ "$?" -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}'..."