Bug 84978

Summary: mbm: connection error when authentication requires special characters
Product: ModemManager Reporter: Aleksander Morgado <aleksander>
Component: pluginsAssignee: ModemManager bug user <modemmanager>
Status: RESOLVED MOVED QA Contact:
Severity: normal    
Priority: medium    
Version: unspecified   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:

Description Aleksander Morgado 2014-10-14 09:16:02 UTC 
Originally reported at:

https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/540003
https://bugzilla.gnome.org/show_bug.cgi?id=632219

The Ericsson/MBM modems don't use PPP for the data connection, as they expose a network interface, and therefore the APN authentication settings (user/pass) are not given to pppd. Instead, ModemManager uses the following command to preconfigure the authentication settings to use before launching the connection:

  AT*EIAAUW=2,1,"username","password"

The given username and password are given in the current charset encoding configured in the modem, which should be UTF-8 preferably.

Now, the problem is that when special characters are required by the operator, e.g. in the username, the connection will not succeeed. E.g. for A1/Austria operator:

  AT*EIAAUW=2,1,"ppp@a1plus.at","ppp"

The issue may therefore be that we either don't pass the username/password encoded properly OR that the modem firmware actually has a bug in that command handling.

Debug logs with MM 1.x are needed.

Also, it would be a good idea to check whether the setting is READ properly after being written, with:
  AT*EIAAUR=2,1

Note that PPP on the TTY with those same username/password will actually work.
Comment 1 Aleksander Morgado 2016-10-24 12:00:33 UTC 
For reference, I'm testing with a F3507g, and it seems that this modem does receive and store the string properly:

AT*EIAAUW=2,1,"ppp@a1plus.at","ppp"
OK

AT*EIAAUR=2,1
*EIAAUR: 2,1,"ppp@a1plus.at","ppp",00111,0
Comment 2 GitLab Migration User 2018-06-10 09:00:07 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mobile-broadband/ModemManager/issues/5.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.