[BUG] TOBY-L210: Bearer's user and password are swapped in +UAUTHREQ command
Baryshnikov, Maxim (Digiteq Automotive)
Maxim.Baryshnikov at digiteqautomotive.com
Fri Oct 26 17:48:00 UTC 2018
Hello everyone,
I would like to report a small bug into bearer's connection on TOBY-L210. Here follows the information about my hardware (from mmcli):
root at zynq7:~# ModemManager --version
ModemManager 1.8.2
Copyright (C) 2008-2017 The ModemManager authors
License GPLv2+: GNU GPL version 2 or later <http://gnu.org/licenses/gpl-2.0.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
root at zynq7:~# mmcli -m 0
/org/freedesktop/ModemManager1/Modem/0 (device id '9be611a4f382a582972f20fa86efbaa8f6b02918')
-------------------------
Hardware | manufacturer: 'u-blox'
| model: 'TOBY-L210'
| revision: '15.63'
| H/W revision: 'unknown'
| supported: 'gsm-umts, lte'
| current: 'gsm-umts, lte'
| equipment id: '############'
-------------------------
System | device: '/sys/devices/soc0/amba/e0002000.usb/ci_hdrc.0/usb1/1-1/1-1.2'
| drivers: 'cdc_acm, cdc_ether'
| plugin: 'u-blox'
| primary port: 'ttyACM1'
| ports: 'ttyACM1 (at), ttyACM0 (at), wwan0 (net), ttyACM2 (at)'
-------------------------
Numbers | own : 'unknown'
-------------------------
Status | lock: 'none'
| unlock retries: 'sim-pin (3), sim-pin2 (3), sim-puk (10), sim-puk2 (10)'
| state: 'enabled'
| power state: 'on'
| access tech: 'unknown'
| signal quality: '40' (recent)
-------------------------
Modes | supported: 'allowed: 2g; preferred: none
| allowed: 2g, 3g; preferred: none
| allowed: 2g, 3g; preferred: 2g
| allowed: 2g, 3g; preferred: 3g
| allowed: 3g; preferred: none
| allowed: 4g; preferred: none
| allowed: 2g, 3g, 4g; preferred: none
| allowed: 2g, 3g, 4g; preferred: 2g
| allowed: 2g, 3g, 4g; preferred: 3g
| allowed: 2g, 3g, 4g; preferred: 4g
| allowed: 2g, 4g; preferred: none
| allowed: 2g, 4g; preferred: 2g
| allowed: 2g, 4g; preferred: 4g
| allowed: 3g, 4g; preferred: none
| allowed: 3g, 4g; preferred: 3g
| allowed: 3g, 4g; preferred: 4g'
| current: 'allowed: 2g, 3g, 4g; preferred: 4g'
-------------------------
Bands | supported: 'egsm, dcs, pcs, g850, utran-1, utran-3, utran-4, utran-6, utran-5, utran-8, utran-2, utran-7, eutran-1, eutran-2, eutran-3, eutran-4, eutran-5, eutran-7, eutran-8, eutran-11, eutran-13, eutran-17, eutran-20, utran-11'
| current: 'egsm, dcs, pcs, g850, utran-3, utran-5, utran-8, utran-2, eutran-2, eutran-3, eutran-5, eutran-8'
-------------------------
IP | supported: 'ipv4, ipv6, ipv4v6'
-------------------------
3GPP | imei: '############'
| enabled locks: 'none'
| operator id: 'unknown'
| operator name: 'unknown'
| subscription: 'unknown'
| registration: 'unknown'
| EPS UE mode: 'csps-2'
-------------------------
SIM | path: '/org/freedesktop/ModemManager1/SIM/0'
-------------------------
Bearers | paths: 'none'
While it is in a router mode and uses ethernet-over-usb interface, I've noticed that when I connect to the bearer, the credentials are swapped in
AT+UAUTHREQ command. The order of user and password is not correct, at least in accordance with TOBY-L2 AT commands manual. You could see it in the log below.
Oct 26 17:13:19 zynq7 ModemManager[10016]: <debug> (ttyACM1) device open count is 2 (open)
Oct 26 17:13:19 zynq7 ModemManager[10016]: <debug> (ttyACM1): --> 'AT+CIND?<CR>'
Oct 26 17:13:19 zynq7 ModemManager[10016]: <debug> (ttyACM1): <-- '<CR><LF>+CIND: 5,2,0,0,0,0,1,0,1,0,0,1<CR><LF>'
Oct 26 17:13:19 zynq7 ModemManager[10016]: <debug> (ttyACM1): <-- '<CR><LF>OK<CR><LF>'
Oct 26 17:13:19 zynq7 ModemManager[10016]: <debug> Modem /org/freedesktop/ModemManager1/Modem/0: signal quality updated (40)
Oct 26 17:13:19 zynq7 ModemManager[10016]: <debug> Periodic signal quality checks scheduled in 30s
Oct 26 17:13:19 zynq7 ModemManager[10016]: <debug> (ttyACM1) device open count is 1 (close)
Oct 26 17:13:19 zynq7 ModemManager[10016]: <debug> Connecting bearer '/org/freedesktop/ModemManager1/Bearer/0'
Oct 26 17:13:19 zynq7 ModemManager[10016]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (registered ->
Oct 26 17:13:19 zynq7 ModemManager[10016]: <debug> Launching 3GPP connection attempt with APN 'testapn'
Oct 26 17:13:19 zynq7 ModemManager[10016]: <debug> Looking for best CID...
Oct 26 17:13:19 zynq7 ModemManager[10016]: <debug> (ttyACM1) device open count is 2 (open)
Oct 26 17:13:19 zynq7 ModemManager[10016]: <debug> (ttyACM1): --> 'AT+CGDCONT?<CR>'
Oct 26 17:13:19 zynq7 ModemManager[10016]: <debug> (ttyACM1): <-- '<CR><LF>+CGDCONT: 1,"IP","testapn","",0,0,0,0,0,0<CR><LF>'
Oct 26 17:13:19 zynq7 ModemManager[10016]: <debug> (ttyACM1): <-- '<CR><LF>OK<CR><LF>'
Oct 26 17:13:19 zynq7 ModemManager[10016]: <debug> Found '1' PDP contexts
Oct 26 17:13:19 zynq7 ModemManager[10016]: <debug> PDP context [cid=1] [type='ipv4'] [apn='testapn']
Oct 26 17:13:19 zynq7 ModemManager[10016]: <debug> Found PDP context with CID 1 and PDP type ipv4 for APN 'testapn'
Oct 26 17:13:19 zynq7 ModemManager[10016]: <debug> Using CHAP authentication method
Oct 26 17:13:19 zynq7 ModemManager[10016]: <debug> setting up authentication preferences in PDP context #1...
Oct 26 17:13:19 zynq7 ModemManager[10016]: <debug> (ttyACM1) device open count is 3 (open)
Oct 26 17:13:19 zynq7 ModemManager[10016]: <debug> (ttyACM1) device open count is 2 (close)
Oct 26 17:13:19 zynq7 ModemManager[10016]: <debug> (ttyACM1): --> 'AT+UAUTHREQ=1,2,"testpassword","testuser"<CR>'
Oct 26 17:13:19 zynq7 ModemManager[10016]: <debug> (ttyACM1): <-- '<CR><LF>OK<CR><LF>'
The credentials were set in the following way:
root at zynq7:~# mmcli -m 0 --create-bearer='apn=testapn,ip-type=ipv4,allowed-auth=chap,password=testpassword,user=testuser,allow-roaming=true'
Successfully created new bearer in modem:
/org/freedesktop/ModemManager1/Bearer/0
root@ zynq7:~# mmcli -m 0 -b 0
Bearer '/org/freedesktop/ModemManager1/Bearer/0'
-------------------------
Status | connected: 'no'
| suspended: 'no'
| interface: 'unknown'
| IP timeout: '20'
-------------------------
Properties | apn: 'testapn'
| roaming: 'allowed'
| IP type: 'ipv4'
| user: 'testuser'
| password: 'testpassword'
| number: 'none'
| Rm protocol: 'unknown'
-------------------------
IPv4 configuration | method: 'unknown'
-------------------------
IPv6 configuration | method: 'unknown'
-------------------------
Stats | Duration: '0'
| Bytes received: 'N/A'
| Bytes transmitted: 'N/A'
If, however, If I put the values otherwise (user=testpassword and password=testuser) in the mmcli command, the connection sets up without any errors.
I did not find another place for bug reporting, so I am sending it here. Thank you in advance for an attention.
Kind regards,
Maxim Baryshnikov.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/modemmanager-devel/attachments/20181026/2c558454/attachment-0001.html>
More information about the ModemManager-devel
mailing list