2021-12-27 09:36:06 |
Jerry Lee |
bug |
|
|
added bug |
2021-12-27 11:40:21 |
Jerry Lee |
description |
[Impact]
Some 4G/5G mobile networks(for ex., AT&T) requires a specific MTU setting, this setting will be exposed by the ModemManager for network-manger to configure the MTU of the modem network interface .
The current modem-manager v1.22.10-1ubuntu2.2 in focal can’t pass AT&T’s modem system certification.
[Fix]
This upstream patch can resolve this bug: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/499/diffs?commit_id=212758ea05a4c13d65f36b55c90aee7919642631
[Test Plan]
1. Use a Lenovo platform SE30 including 4G Quectel EM160 modem and an AT&T SIM card in US
2. Enable 4G modem and connect to AT&T apn
$ sudo mmcli -i 0 --pin=0000
$ sudo mmcli --modem 0 --enable
$ sudo mmcli -m 0 --simple-connect="pin=0000,apn=emome"
$ sudo nmcli radio wwan on
$ sudo nmcli connection add type gsm ifname wwan0p2MBIM con-name mymodem apn emome
$ sudo nmcli connection up id mymodem
3. Check if the MTU got from the following results are the same:
$ sudo mmcli --bearer 5 | mtu
$ ifconfig mhi_mbim0 | grep mtu
* Expected result:
Both MTUs are the same value 1430
* Actual tested result:
Different values (one is 1430 , another is 1500)
[Where problems could occur]
Very low.
This is a simple fix: network-manager gets the MTU from the ModemManager then sets the MTU of the modem interface.
[Other info]
$ lsb_release -rd
Description: Ubuntu 20.04.3 LTS
Release: 20.04 |
[Impact]
Some 4G/5G mobile networks(for ex., AT&T) requires a specific MTU setting, this setting will be exposed by the ModemManager for network-manger to configure the MTU of the modem network interface .
The current modem-manager v1.22.10-1ubuntu2.2 in focal can’t pass AT&T’s modem system certification.
[Fix]
This upstream patch can resolve this bug: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/499/diffs?commit_id=212758ea05a4c13d65f36b55c90aee7919642631
[Test Plan]
1. Use a Lenovo platform SE30 including 4G Quectel EM160 modem and an AT&T SIM card in US
2. Enable 4G modem and connect to AT&T apn
$ sudo mmcli -i 0 --pin=0000
$ sudo mmcli --modem 0 --enable
$ sudo mmcli -m 0 --simple-connect="pin=0000,apn=emome"
$ sudo nmcli radio wwan on
$ sudo nmcli connection add type gsm ifname wwan0p2MBIM con-name mymodem apn emome
$ sudo nmcli connection up id mymodem
3. Check if the MTU got from the following results are the same:
$ sudo mmcli --bearer 5 | mtu
$ ifconfig mhi_mbim0 | grep mtu
* Expected result:
Both MTUs are the same value 1430
* Actual tested result:
Different values (one is 1430 , another is 1500)
[Where problems could occur]
Very low.
This is a simple fix: network-manager gets the MTU from the ModemManager then sets the MTU of the modem interface.
[Other info]
1. Network-manager v1.30.0-1ubuntu3 in hirsute has included the fix. |
|
2021-12-27 11:45:19 |
Jerry Lee |
attachment added |
|
.debdiff for focal https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1955797/+attachment/5549698/+files/network-manager_1-1.22.10-1ubuntu2.3-focal.debdiff |
|
2021-12-27 12:27:54 |
Ubuntu Foundations Team Bug Bot |
tags |
oem-priority |
oem-priority patch |
|
2021-12-27 12:28:03 |
Ubuntu Foundations Team Bug Bot |
bug |
|
|
added subscriber Ubuntu Sponsors Team |
2021-12-28 10:44:28 |
Launchpad Janitor |
network-manager (Ubuntu): status |
New |
Confirmed |
|
2021-12-28 10:46:46 |
Mathew Hodson |
nominated for series |
|
Ubuntu Focal |
|
2021-12-28 10:46:46 |
Mathew Hodson |
bug task added |
|
network-manager (Ubuntu Focal) |
|
2021-12-28 10:46:53 |
Mathew Hodson |
network-manager (Ubuntu): importance |
Undecided |
Medium |
|
2021-12-28 10:46:55 |
Mathew Hodson |
network-manager (Ubuntu Focal): importance |
Undecided |
Medium |
|
2021-12-28 10:47:00 |
Mathew Hodson |
network-manager (Ubuntu): status |
Confirmed |
Fix Released |
|
2022-01-13 10:19:37 |
Łukasz Zemczak |
removed subscriber Ubuntu Sponsors Team |
|
|
|
2022-01-18 18:33:09 |
Brian Murray |
network-manager (Ubuntu Focal): status |
New |
Fix Committed |
|
2022-01-18 18:33:10 |
Brian Murray |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
2022-01-18 18:33:12 |
Brian Murray |
bug |
|
|
added subscriber SRU Verification |
2022-01-18 18:33:15 |
Brian Murray |
tags |
oem-priority patch |
oem-priority patch verification-needed verification-needed-focal |
|
2022-01-21 11:09:09 |
Jerry Lee |
attachment added |
|
Verification report https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1955797/+attachment/5556131/+files/SRU%20for%20network-manager%28verify%20report%29%20.pdf |
|
2022-01-21 11:11:14 |
Jerry Lee |
tags |
oem-priority patch verification-needed verification-needed-focal |
oem-priority patch verification-done-focal verification-needed |
|
2022-01-28 05:17:36 |
Jerry Lee |
description |
[Impact]
Some 4G/5G mobile networks(for ex., AT&T) requires a specific MTU setting, this setting will be exposed by the ModemManager for network-manger to configure the MTU of the modem network interface .
The current modem-manager v1.22.10-1ubuntu2.2 in focal can’t pass AT&T’s modem system certification.
[Fix]
This upstream patch can resolve this bug: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/499/diffs?commit_id=212758ea05a4c13d65f36b55c90aee7919642631
[Test Plan]
1. Use a Lenovo platform SE30 including 4G Quectel EM160 modem and an AT&T SIM card in US
2. Enable 4G modem and connect to AT&T apn
$ sudo mmcli -i 0 --pin=0000
$ sudo mmcli --modem 0 --enable
$ sudo mmcli -m 0 --simple-connect="pin=0000,apn=emome"
$ sudo nmcli radio wwan on
$ sudo nmcli connection add type gsm ifname wwan0p2MBIM con-name mymodem apn emome
$ sudo nmcli connection up id mymodem
3. Check if the MTU got from the following results are the same:
$ sudo mmcli --bearer 5 | mtu
$ ifconfig mhi_mbim0 | grep mtu
* Expected result:
Both MTUs are the same value 1430
* Actual tested result:
Different values (one is 1430 , another is 1500)
[Where problems could occur]
Very low.
This is a simple fix: network-manager gets the MTU from the ModemManager then sets the MTU of the modem interface.
[Other info]
1. Network-manager v1.30.0-1ubuntu3 in hirsute has included the fix. |
[Impact]
Some 4G/5G mobile networks(for ex., AT&T) requires a specific MTU setting, this setting will be exposed by the ModemManager for network-manger to configure the MTU of the modem network interface .
The current network-manager v1.22.10-1ubuntu2.2 in focal can’t pass AT&T’s modem system certification.
[Fix]
This upstream patch can resolve this bug: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/499/diffs?commit_id=212758ea05a4c13d65f36b55c90aee7919642631
[Test Plan]
1. Use a Lenovo platform SE30 including 4G Quectel EM160 modem and an AT&T SIM card in US
2. Enable 4G modem and connect to AT&T apn
$ sudo mmcli -i 0 --pin=0000
$ sudo mmcli --modem 0 --enable
$ sudo mmcli -m 0 --simple-connect="pin=0000,apn=emome"
$ sudo nmcli radio wwan on
$ sudo nmcli connection add type gsm ifname wwan0p2MBIM con-name mymodem apn emome
$ sudo nmcli connection up id mymodem
3. Check if the MTU got from the following results are the same:
$ sudo mmcli --bearer 5 | mtu
$ ifconfig mhi_mbim0 | grep mtu
* Expected result:
Both MTUs are the same value 1430
* Actual tested result:
Different values (one is 1430 , another is 1500)
[Where problems could occur]
Very low.
This is a simple fix: network-manager gets the MTU from the ModemManager then sets the MTU of the modem interface.
[Other info]
1. Network-manager v1.30.0-1ubuntu3 in hirsute has included the fix. |
|
2022-02-01 17:41:13 |
Brian Murray |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
2022-02-01 17:54:44 |
Launchpad Janitor |
network-manager (Ubuntu Focal): status |
Fix Committed |
Fix Released |
|