Regression regarding ip_type when updating from 1.10.4 to 1.12.0

Fri Nov 8 13:20:11 UTC 2019

Hello,

I recently tried updating to the new version of ModemManager

Previous versions:

- ModemManager 1.10.4
- libmbim 1.18.2

New versions:

- ModemManager 1.12.0
- libmbim 1.20.2

The test device is a Lenovo T470s with a Sierra Wireless EM7455. The provider is vodafone.de

We configure our bearer with the ip_type MM_BEARER_IP_FAMILY_IPV4V6. We assumed this means that IPv4 or IPv6 or both should be configured, whatever provided by the network.

In our tests this worked correctly with the version 1.10.4 of ModemManager, when using a SIM from vodafone we got IPv4 connectivitiy, with a SIM from telekom we got both IPv4 and IPv6 connectivity.

However, after updating to version 1.12.0 strange behaviour occured. The first view connections after a cold boot of the device failed with:

2019-11-08 09:54:31.286 modem-manager.service: [/dev/cdc-wdm0] Received message (translated)...
                                               >>>>>> Header:
                                               >>>>>>   length      = 84
                                               >>>>>>   type        = command-done (0x80000003)
                                               >>>>>>   transaction = 45
                                               >>>>>> Fragment header:
                                               >>>>>>   total   = 1
                                               >>>>>>   current = 0
                                               >>>>>> Contents:
                                               >>>>>>   status error = 'None' (0x00000000)
                                               >>>>>>   service      = 'basic-connect' (a289cc33-bcbb-8b4f-b6b0-133ec2aae6df)
                                               >>>>>>   cid          = 'connect' (0x0000000c)
                                               >>>>>> Fields:
                                               >>>>>>   SessionId = '0'
                                               >>>>>>   ActivationState = 'activated'
                                               >>>>>>   VoiceCallState = 'none'
                                               >>>>>>   IpType = 'ipv4'
                                               >>>>>>   ContextType = '7e5e2a7e-4e6f-7272-736b-656e7e5e2a7e'
                                               >>>>>>   NwError = '50'
2019-11-08 09:54:31.286 modem-manager.service: [1573206871.286147] Couldn't connect bearer '/org/freedesktop/ModemManager1/Bearer/0': 'Unknown error (50)'

At this moment the access tech was shown as: HSDPA | HSUPA

A little later the access tech changed to LTE and I was able to connect with this setting:

2019-11-08 09:55:12.822 modem-manager.service: [1573206912.822471] IPv4 configuration available: 'address, gateway, dns, mtu'
2019-11-08 09:55:12.822 modem-manager.service: [1573206912.822519]   IP addresses (1)
2019-11-08 09:55:12.823 modem-manager.service: [1573206912.822576]     IP [0]: '100.96.188.174/30'
2019-11-08 09:55:12.823 modem-manager.service: [1573206912.822625]   Gateway: '100.96.188.173'
2019-11-08 09:55:12.823 modem-manager.service: [1573206912.822660]   DNS addresses (2)
2019-11-08 09:55:12.823 modem-manager.service: [1573206912.822706]     DNS [0]: '139.7.30.126'
2019-11-08 09:55:12.823 modem-manager.service: [1573206912.822753]     DNS [1]: '139.7.30.125'
2019-11-08 09:55:12.824 modem-manager.service: [1573206912.822784]   MTU: '1500'
2019-11-08 09:55:12.824 modem-manager.service: [1573206912.822812] IPv6 configuration available: 'none'
2019-11-08 09:55:12.824 modem-manager.service: [1573206912.822961] (wwan0): port now connected
2019-11-08 09:55:12.824 modem-manager.service: [1573206912.823046] Connected bearer '/org/freedesktop/ModemManager1/Bearer/2'

The strange thing is, when I change the ip_type in the bearer to MM_BEARER_IP_FAMILY_ANY the connection works on the first try:

2019-11-08 12:58:42.156 modem-manager.service: [1573217922.156045] IPv4 configuration available: 'address, gateway, dns, mtu'
2019-11-08 12:58:42.156 modem-manager.service: [1573217922.156101]   IP addresses (1)
2019-11-08 12:58:42.156 modem-manager.service: [1573217922.156164]     IP [0]: '100.83.127.55/28'
2019-11-08 12:58:42.156 modem-manager.service: [1573217922.156199]   Gateway: '100.83.127.56'
2019-11-08 12:58:42.157 modem-manager.service: [1573217922.156223]   DNS addresses (2)
2019-11-08 12:58:42.157 modem-manager.service: [1573217922.156254]     DNS [0]: '139.7.30.126'
2019-11-08 12:58:42.157 modem-manager.service: [1573217922.156285]     DNS [1]: '139.7.30.125'
2019-11-08 12:58:42.157 modem-manager.service: [1573217922.156307]   MTU: '1500'
2019-11-08 12:58:42.158 modem-manager.service: [1573217922.156326] IPv6 configuration available: 'none'
2019-11-08 12:58:42.158 modem-manager.service: [1573217922.156444] (wwan0): port now connected
2019-11-08 12:58:42.158 modem-manager.service: [1573217922.156476] Connected bearer '/org/freedesktop/ModemManager1/Bearer/0'

Has the interpretation of the ip_type MM_BEARER_IP_FAMILY_IPV4V6 changed when performing the connect?

I have attached the connection attempts with MM_BEARER_IP_FAMILY_IPV4V6 as modem-manager-ipv4v6.log.gz. In this log file the bearers 0 and 1 fail to connect, then the access technology changes to LTE and bearer 2 can successfully connect.

The log file modem-manager-ip-any.log.gz contains the test with MM_BEARER_IP_FAMILY_ANY.

Thanks,

	Torsten

-------------- next part --------------
A non-text attachment was scrubbed...
Name: modem-manager-ipv4v6.log.gz
Type: application/gzip
Size: 39793 bytes
Desc: not available
URL: <https://lists.freedesktop.org/archives/modemmanager-devel/attachments/20191108/4dc7bd15/attachment-0002.gz>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: modem-manager-ip-any.log.gz
Type: application/gzip
Size: 42745 bytes
Desc: not available
URL: <https://lists.freedesktop.org/archives/modemmanager-devel/attachments/20191108/4dc7bd15/attachment-0003.gz>