You are not logged in.
- Topics: Active | Unanswered
#1 2022-04-10 22:05:24
- weltenseglr
- Member
- Registered: 2022-04-10
- Posts: 6
no IPv6 with ModemManager/NetworkManager
Hi,
I could use some help or input... I own a ThinkPad with a Sierra Wireless EM7455 modem which worked like a charm for months.
However, about three weeks ago I noticed that IPv6 wasn't available anymore on my wwan.
from my logs I got:
Apr 10 23:28:17 moerklbook5 NetworkManager[603]: <info> [1649626097.5027] device (cdc-wdm0): Activation: starting connection 'O2' (24b5fcd7-5224-4f87-86d0-fcb047d68c06)
Apr 10 23:28:17 moerklbook5 NetworkManager[603]: <info> [1649626097.5031] audit: op="connection-activate" uuid="24b5fcd7-5224-4f87-86d0-fcb047d68c06" name="O2" pid=1099 uid=1000 result="success"
Apr 10 23:28:17 moerklbook5 NetworkManager[603]: <info> [1649626097.5033] device (cdc-wdm0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Apr 10 23:28:17 moerklbook5 NetworkManager[603]: <info> [1649626097.8069] device (cdc-wdm0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Apr 10 23:28:17 moerklbook5 NetworkManager[603]: <info> [1649626097.8218] device (cdc-wdm0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Apr 10 23:28:17 moerklbook5 NetworkManager[603]: <info> [1649626097.8229] modem-broadband[cdc-wdm0]: IPv4 static configuration:
Apr 10 23:28:17 moerklbook5 NetworkManager[603]: <info> [1649626097.8230] modem-broadband[cdc-wdm0]: address 10.34.109.118/30 brd* 10.34.109.119 lft forever pref forever lifetime 1211-0[0,0] src wwan
Apr 10 23:28:17 moerklbook5 NetworkManager[603]: <info> [1649626097.8231] modem-broadband[cdc-wdm0]: gateway 10.34.109.117
Apr 10 23:28:17 moerklbook5 NetworkManager[603]: <info> [1649626097.8231] modem-broadband[cdc-wdm0]: DNS 62.109.121.17
Apr 10 23:28:17 moerklbook5 NetworkManager[603]: <info> [1649626097.8231] modem-broadband[cdc-wdm0]: DNS 62.109.121.18
Apr 10 23:28:17 moerklbook5 NetworkManager[603]: <info> [1649626097.8231] modem-broadband[cdc-wdm0]: MTU 1500
Apr 10 23:28:17 moerklbook5 NetworkManager[603]: <info> [1649626097.8232] modem-broadband[cdc-wdm0]: IPv6 base configuration:
Apr 10 23:28:17 moerklbook5 NetworkManager[603]: <info> [1649626097.8233] modem-broadband[cdc-wdm0]: address 2a02:3032:1:3a1e:e86b:c2b7:1f6c:297b/64 lft forever pref forever lifetime 1211-0[0,0] src unknown (slaac disabled)
Apr 10 23:28:17 moerklbook5 NetworkManager[603]: <info> [1649626097.8233] modem-broadband[cdc-wdm0]: gateway 2a02:3032:1:3a1e:d142:cab5:7f1a:7bae
Apr 10 23:28:17 moerklbook5 NetworkManager[603]: <info> [1649626097.8234] modem-broadband[cdc-wdm0]: DNS 2a02:3018:0:40ff::aaaa
Apr 10 23:28:17 moerklbook5 NetworkManager[603]: <info> [1649626097.8234] modem-broadband[cdc-wdm0]: DNS 2a02:3018:0:40ff::bbbb
Apr 10 23:28:17 moerklbook5 NetworkManager[603]: <warn> [1649626097.8252] platform-linux: do-add-ip6-address[3: 2a02:3032:1:3a1e:e86b:c2b7:1f6c:297b]: failure 13 (Permission denied)
Apr 10 23:28:17 moerklbook5 NetworkManager[603]: <info> [1649626097.8258] device (cdc-wdm0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Apr 10 23:28:17 moerklbook5 NetworkManager[603]: <info> [1649626097.8526] device (cdc-wdm0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Apr 10 23:28:17 moerklbook5 NetworkManager[603]: <info> [1649626097.8529] device (cdc-wdm0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Apr 10 23:28:17 moerklbook5 NetworkManager[603]: <info> [1649626097.8535] policy: set 'O2' (wwp0s20f0u6i12) as default for IPv6 routing and DNS
Apr 10 23:28:17 moerklbook5 dnsmasq[1017]: setting upstream servers from DBus
Apr 10 23:28:17 moerklbook5 dnsmasq[1017]: using nameserver 2a02:3018:0:40ff::aaaa#53(via wwp0s20f0u6i12)
Apr 10 23:28:17 moerklbook5 dnsmasq[1017]: using nameserver 2a02:3018:0:40ff::aaaa#53 for domain e.1.a.3.1.0.0.0.2.3.0.3.2.0.a.2.ip6.arpa (no DNSSEC)
Apr 10 23:28:17 moerklbook5 dnsmasq[1017]: using nameserver 2a02:3018:0:40ff::bbbb#53(via wwp0s20f0u6i12)
Apr 10 23:28:17 moerklbook5 dnsmasq[1017]: using nameserver 2a02:3018:0:40ff::bbbb#53 for domain e.1.a.3.1.0.0.0.2.3.0.3.2.0.a.2.ip6.arpa (no DNSSEC)
Apr 10 23:28:17 moerklbook5 dnsmasq[1017]: using nameserver 2a02:2970:1002::18#53 for domain 0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa (no DNSSEC)
Apr 10 23:28:17 moerklbook5 dnsmasq[1017]: using nameserver 62.109.121.17#53 for domain 116.109.34.10.in-addr.arpa (no DNSSEC)
Apr 10 23:28:17 moerklbook5 dnsmasq[1017]: using nameserver 62.109.121.17#53 for domain 117.109.34.10.in-addr.arpa (no DNSSEC)
Apr 10 23:28:17 moerklbook5 dnsmasq[1017]: using nameserver 62.109.121.17#53 for domain 118.109.34.10.in-addr.arpa (no DNSSEC)
Apr 10 23:28:17 moerklbook5 dnsmasq[1017]: using nameserver 62.109.121.17#53 for domain 119.109.34.10.in-addr.arpa (no DNSSEC)
Apr 10 23:28:17 moerklbook5 dnsmasq[1017]: using nameserver 62.109.121.18#53 for domain 116.109.34.10.in-addr.arpa (no DNSSEC)
Apr 10 23:28:17 moerklbook5 dnsmasq[1017]: using nameserver 62.109.121.18#53 for domain 117.109.34.10.in-addr.arpa (no DNSSEC)
Apr 10 23:28:17 moerklbook5 dnsmasq[1017]: using nameserver 62.109.121.18#53 for domain 118.109.34.10.in-addr.arpa (no DNSSEC)
Apr 10 23:28:17 moerklbook5 dnsmasq[1017]: using nameserver 62.109.121.18#53 for domain 119.109.34.10.in-addr.arpa (no DNSSEC)
Apr 10 23:28:17 moerklbook5 dnsmasq[1017]: cleared cache
Apr 10 23:28:17 moerklbook5 NetworkManager[603]: <info> [1649626097.8871] device (cdc-wdm0): Activation: successful, device activated.The warning [1649626097.8252] platform-linux: do-add-ip6-address[3: 2a02:3032:1:3a1e:e86b:c2b7:1f6c:297b]: failure 13 (Permission denied) made me wonder... So I checked sysctl:
$ sysctl net.ipv6.conf.wwp0s20f0u6i12.disable_ipv6
net.ipv6.conf.wwp0s20f0u6i12.disable_ipv6 = 1
$ ip addr show dev wwp0s20f0u6i12
3: wwp0s20f0u6i12: <BROADCAST,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000
link/ether 66:18:xx:xx:xx:xx brd ff:ff:ff:ff:ff:ff
inet 10.34.109.118/30 brd 10.34.109.119 scope global noprefixroute wwp0s20f0u6i12
valid_lft forever preferred_lft foreverAt first I thought this would be an easy fix. But it wasn't. Setting net.ipv6.conf.wwp0s20f0u6i12.disable_ipv6=0 won't do the trick (not sysctl -w nor setting in /etc/sysctl.d/...). As soon I reconnect my wwan, disable_ipv6 will be back to 1.
Do you have any idea how to fix this? Any help would be appriciated!!
Offline
#2 2022-04-11 06:25:07
- -thc
- Member
- Registered: 2017-03-15
- Posts: 500
Re: no IPv6 with ModemManager/NetworkManager
Please check
sysctl net.ipv6.conf.all.disable_ipv6and
nmcli c show 'Connection name' | grep ipv6.methodOffline
#3 2022-04-11 07:22:03
- weltenseglr
- Member
- Registered: 2022-04-10
- Posts: 6
Re: no IPv6 with ModemManager/NetworkManager
Sorry I didn't post them. They seem to be okay. Dual stack is working on all other interfaces.
$ nmcli c show 'O2' | grep ipv6.method
ipv6.method: auto
$ sysctl net.ipv6.conf.all.disable_ipv6
net.ipv6.conf.all.disable_ipv6 = 0Last edited by weltenseglr (2022-04-11 07:22:19)
Offline
#4 2022-04-11 07:32:45
- -thc
- Member
- Registered: 2017-03-15
- Posts: 500
Re: no IPv6 with ModemManager/NetworkManager
Strange - and I guess manually setting the IPv6 address doesn't work either?
ip addr add 2a02:3032:1:3a1e:e86b:c2b7:1f6c:297b dev device_nameOffline
#5 2022-04-11 08:08:28
- weltenseglr
- Member
- Registered: 2022-04-10
- Posts: 6
Re: no IPv6 with ModemManager/NetworkManager
you're right! This doesn't work either. Well, it works, as long as won't activate my nm connection.
As root I get a
RTNETLINK answers: Permission deniedwhich is consistent with the reappearing of
$ sysctl net.ipv6.conf.wwp0s20f0u6i12.disable_ipv6
net.ipv6.conf.wwp0s20f0u6i12.disable_ipv6 = 1see
$ nmcli connection down O2
Connection 'O2' successfully deactivated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/4)
$ sudo sysctl -w net.ipv6.conf.wwp0s20f0u6i12.disable_ipv6=0
net.ipv6.conf.wwp0s20f0u6i12.disable_ipv6 = 0
$ sudo ip addr add 2a02:3032:1:3a1e:e86b:c2b7:1f6c:297b dev wwp0s20f0u6i12
$ ip -6 addr show dev wwp0s20f0u6i12
3: wwp0s20f0u6i12: <BROADCAST,MULTICAST,NOARP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
inet6 2a02:3032:1:3a1e:e86b:c2b7:1f6c:297b/128 scope global
valid_lft forever preferred_lft forever
$ nmcli connection up O2
Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/5)
$ sysctl net.ipv6.conf.wwp0s20f0u6i12.disable_ipv6
net.ipv6.conf.wwp0s20f0u6i12.disable_ipv6 = 1
$ ip addr show dev wwp0s20f0u6i12
3: wwp0s20f0u6i12: <BROADCAST,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000
link/ether 66:18:xx:xx:xx:xx brd ff:ff:ff:ff:ff:ff
inet 10.32.183.173/30 brd 10.32.183.175 scope global noprefixroute wwp0s20f0u6i12
valid_lft forever preferred_lft foreverEDIT: Profile might be usefull
[connection]
id=O2
uuid=24b5fcd7-5224-4f87-86d0-fcb047d68c06
type=gsm
[gsm]
apn=internet
number=*99#
password-flags=4
pin=****
sim-id=***********************
[ppp]
refuse-chap=true
refuse-eap=true
refuse-mschap=true
refuse-mschapv2=true
[ipv4]
dns-priority=120
method=auto
route-metric=1050
[ipv6]
method=autoI just can't find out why ipv6 gets disabled...
Last edited by weltenseglr (2022-04-11 08:15:15)
Offline
#6 2022-04-11 10:05:31
- -thc
- Member
- Registered: 2017-03-15
- Posts: 500
Re: no IPv6 with ModemManager/NetworkManager
Last straw: This should be 0 (- this setting slips my mind) :
sysctl net.ipv6.conf.default.disable_ipv6Offline
#7 2022-04-12 03:54:00
- weltenseglr
- Member
- Registered: 2022-04-10
- Posts: 6
Re: no IPv6 with ModemManager/NetworkManager
Well, that's the weird thing. It is, IPv6 IS working on any interface but WWAN.
Here it's 0 after boot and when I try to connect it turns 1:
At first I thought this would be an easy fix. But it wasn't. Setting net.ipv6.conf.wwp0s20f0u6i12.disable_ipv6=0 won't do the trick (not sysctl -w nor setting in /etc/sysctl.d/...). As soon I reconnect my wwan, disable_ipv6 will be back to 1.
$ sudo sysctl net.ipv6.conf.wwp0s20f0u6i12.disable_ipv6=0
net.ipv6.conf.wwp0s20f0u6i12.disable_ipv6 = 0
$ nmcli connection up O2
Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/5)
$ sysctl net.ipv6.conf.wwp0s20f0u6i12.disable_ipv6
net.ipv6.conf.wwp0s20f0u6i12.disable_ipv6 = 1Last edited by weltenseglr (2022-04-12 04:25:55)
Offline
#8 2022-04-12 07:04:59
- -thc
- Member
- Registered: 2017-03-15
- Posts: 500
Re: no IPv6 with ModemManager/NetworkManager
It's almost as if the driver, the SIM or the service provider deny IPv6.
Offline
#9 2022-04-12 10:34:37
- Lone_Wolf
- Member
- From: Netherlands, Europe
- Registered: 2005-10-04
- Posts: 11,919
Re: no IPv6 with ModemManager/NetworkManager
Can you try setting up the connection manually using mmcli from modemmanager ?
This would help to narrow down probable causes.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
(A works at time B) && (time C > time B ) ≠ (A works at time C)
Offline
#10 2022-04-16 20:37:38
- weltenseglr
- Member
- Registered: 2022-04-10
- Posts: 6
Re: no IPv6 with ModemManager/NetworkManager
Thank you for your message!
$ mmcli -L
/org/freedesktop/ModemManager1/Modem/0 [Sierra Wireless, Incorporated] Sierra Wireless EM7455 Qualcomm Snapdragon X7 LTE-A
$ mmcli -m 0 --simple-connect="apn=internet"
successfully connected the modem
$ sysctl net.ipv6.conf.wwp0s20f0u6i12.disable_ipv6
net.ipv6.conf.wwp0s20f0u6i12.disable_ipv6 = 0
$ mmcli -m 0
-----------------------------
General | path: /org/freedesktop/ModemManager1/Modem/0
| device id: 75a43fd284366ac7c638d4110a506acba6d9a53b
-----------------------------
Hardware | manufacturer: Sierra Wireless, Incorporated
| model: Sierra Wireless EM7455 Qualcomm Snapdragon X7 LTE-A
| firmware revision: SWI9X30C_02.33.03.00
| carrier config: default
| h/w revision: EM7455
| supported: gsm-umts, lte
| current: gsm-umts, lte
| equipment id: 015105003658648
-----------------------------
System | device: /sys/devices/pci0000:00/0000:00:14.0/usb1/1-6
| drivers: cdc_mbim
| plugin: sierra
| primary port: cdc-wdm0
| ports: cdc-wdm0 (mbim), wwp0s20f0u6i12 (net)
-----------------------------
Status | unlock retries: sim-pin2 (3)
| state: connected
| power state: on
| access tech: lte
| signal quality: 19% (cached)
-----------------------------
Modes | supported: allowed: 3g; preferred: none
| allowed: 4g; preferred: none
| allowed: 3g, 4g; preferred: 4g
| allowed: 3g, 4g; preferred: 3g
| current: allowed: 3g, 4g; preferred: 4g
-----------------------------
Bands | supported: utran-1, utran-3, utran-4, utran-5, utran-8, utran-2,
| eutran-1, eutran-2, eutran-3, eutran-4, eutran-5, eutran-7, eutran-8,
| eutran-12, eutran-13, eutran-20, eutran-25, eutran-26, eutran-41
| current: utran-1, utran-3, utran-4, utran-5, utran-8, utran-2,
| eutran-1, eutran-2, eutran-3, eutran-4, eutran-5, eutran-7, eutran-8,
| eutran-12, eutran-13, eutran-20, eutran-25, eutran-26, eutran-41
-----------------------------
IP | supported: ipv4, ipv6, ipv4v6
-----------------------------
3GPP | imei: 0151.....
| enabled locks: fixed-dialing
| operator id: 26203
| operator name: o2 - de
| registration: home
-----------------------------
SIM | primary sim path: /org/freedesktop/ModemManager1/SIM/0
-----------------------------
Bearer | paths: /org/freedesktop/ModemManager1/Bearer/0
$ mmcli --modem 0 --bearer=0 --output-keyvalue
bearer.dbus-path : /org/freedesktop/ModemManager1/Bearer/0
bearer.type : default
bearer.status.connected : yes
bearer.status.connection-error.name : --
bearer.status.connection-error.message : --
bearer.status.suspended : no
bearer.status.multiplexed : no
bearer.status.interface : wwp0s20f0u6i12
bearer.status.ip-timeout : 20
bearer.status.profile-id : --
bearer.properties.apn : internet
bearer.properties.apn-type : --
bearer.properties.roaming : allowed
bearer.properties.ip-type : --
bearer.properties.allowed-auth : --
bearer.properties.user : --
bearer.properties.password : --
bearer.properties.profile-id : --
bearer.properties.rm-protocol : --
bearer.ipv4-config.method : static
bearer.ipv4-config.address : 10.127.65.146
bearer.ipv4-config.prefix : 30
bearer.ipv4-config.gateway : 10.127.65.145
bearer.ipv4-config.dns.length : 2
bearer.ipv4-config.dns.value[1] : 62.109.121.17
bearer.ipv4-config.dns.value[2] : 62.109.121.18
bearer.ipv4-config.mtu : 1500
bearer.ipv6-config.method : --
bearer.ipv6-config.address : --
bearer.ipv6-config.prefix : --
bearer.ipv6-config.gateway : --
bearer.ipv6-config.dns : --
bearer.ipv6-config.mtu : --
bearer.stats.duration : 30
bearer.stats.bytes-rx : --
bearer.stats.bytes-tx : --
bearer.stats.attempts : 1
bearer.stats.failed-attempts : --
bearer.stats.total-duration : 30
bearer.stats.total-bytes-rx : --
bearer.stats.total-bytes-tx : --I'm confused, that there's no ipv6 config, but net.ipv6.conf.wwp0s20f0u6i12.disable_ipv6 = 0 remains
The modem status is different when using NetworkManager. Then I have two bearers and net.ipv6.conf.wwp0s20f0u6i12.disable_ipv6 was set to 1
$ mmcli --modem 0 --bearer=0 --output-keyvalue
bearer.dbus-path : /org/freedesktop/ModemManager1/Bearer/0
bearer.type : default
bearer.status.connected : no
bearer.status.connection-error.name : --
bearer.status.connection-error.message : --
bearer.status.suspended : no
bearer.status.multiplexed : no
bearer.status.interface : --
bearer.status.ip-timeout : 20
bearer.status.profile-id : --
bearer.properties.apn : internet
bearer.properties.apn-type : --
bearer.properties.roaming : allowed
bearer.properties.ip-type : --
bearer.properties.allowed-auth : --
bearer.properties.user : --
bearer.properties.password : --
bearer.properties.profile-id : --
bearer.properties.rm-protocol : --
bearer.ipv4-config.method : --
bearer.ipv4-config.address : --
bearer.ipv4-config.prefix : --
bearer.ipv4-config.gateway : --
bearer.ipv4-config.dns : --
bearer.ipv4-config.mtu : --
bearer.ipv6-config.method : --
bearer.ipv6-config.address : --
bearer.ipv6-config.prefix : --
bearer.ipv6-config.gateway : --
bearer.ipv6-config.dns : --
bearer.ipv6-config.mtu : --
bearer.stats.duration : 75
bearer.stats.bytes-rx : --
bearer.stats.bytes-tx : --
bearer.stats.attempts : 1
bearer.stats.failed-attempts : --
bearer.stats.total-duration : 75
bearer.stats.total-bytes-rx : --
bearer.stats.total-bytes-tx : --
$ mmcli --modem 0 --bearer=1 --output-keyvalue
bearer.dbus-path : /org/freedesktop/ModemManager1/Bearer/1
bearer.type : default
bearer.status.connected : yes
bearer.status.connection-error.name : --
bearer.status.connection-error.message : --
bearer.status.suspended : no
bearer.status.multiplexed : no
bearer.status.interface : wwp0s20f0u6i12
bearer.status.ip-timeout : 20
bearer.status.profile-id : --
bearer.properties.apn : internet
bearer.properties.apn-type : --
bearer.properties.roaming : allowed
bearer.properties.ip-type : ipv4v6
bearer.properties.allowed-auth.length : 2
bearer.properties.allowed-auth.value[1] : none
bearer.properties.allowed-auth.value[2] : pap
bearer.properties.user : --
bearer.properties.password : --
bearer.properties.profile-id : --
bearer.properties.rm-protocol : --
bearer.ipv4-config.method : static
bearer.ipv4-config.address : 10.112.162.21
bearer.ipv4-config.prefix : 30
bearer.ipv4-config.gateway : 10.112.162.22
bearer.ipv4-config.dns.length : 2
bearer.ipv4-config.dns.value[1] : 62.109.121.17
bearer.ipv4-config.dns.value[2] : 62.109.121.18
bearer.ipv4-config.mtu : 1500
bearer.ipv6-config.method : static
bearer.ipv6-config.address : 2a02:3030:80f:9666:9ce9:d9c6:7cff:9435
bearer.ipv6-config.prefix : 64
bearer.ipv6-config.gateway : 2a02:3030:80f:9666:70b6:8952:a446:d669
bearer.ipv6-config.dns.length : 2
bearer.ipv6-config.dns.value[1] : 2a02:3018:0:40ff::aaaa
bearer.ipv6-config.dns.value[2] : 2a02:3018:0:40ff::bbbb
bearer.ipv6-config.mtu : 1500
bearer.stats.duration : 210
bearer.stats.bytes-rx : --
bearer.stats.bytes-tx : --
bearer.stats.attempts : 1
bearer.stats.failed-attempts : --
bearer.stats.total-duration : 210
bearer.stats.total-bytes-rx : --
bearer.stats.total-bytes-tx : --I booted into a Fedora Live I got from a colleague, and my modem just worked after symlinking the fcc unlock (as expected and as it used to some time ago in arch), but I didn't check the bearers.
Any Ideas?
Last edited by weltenseglr (2022-04-16 20:43:29)
Offline
#11 2022-04-17 10:35:31
- Lone_Wolf
- Member
- From: Netherlands, Europe
- Registered: 2005-10-04
- Posts: 11,919
Re: no IPv6 with ModemManager/NetworkManager
Outputs indicate the problem is not with the network client, but somewhere else.
modemmanager on archlinux saw its last update on 12 february 2022 , mobile-broadband-provider-info was updated on 29 march 2022 .
However, about three weeks ago I noticed that IPv6 wasn't available anymore on my wwan.
Please check your pacman log to see when you updated modemmanager & mobile-broadband-provider-info .
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
(A works at time B) && (time C > time B ) ≠ (A works at time C)
Offline
#12 2022-04-19 12:49:09
- weltenseglr
- Member
- Registered: 2022-04-10
- Posts: 6
Re: no IPv6 with ModemManager/NetworkManager
I updated modemmanager on Feb 13 and mobile-broadband-provider-info on Mar 29.
I know for sure that ipv6 has been working on Mar 15.
Today I upgraded my ssd and did a clean install. However, still no ipv6 on wwan.
From Fedora I know that a modemmanager=1.18.2 and mobile-broadband-provider-info=20210805 are working, however neither rolling back to these versions nor installing them in the first place helps.
Am I right to conclude that that's not an issue with modemmanager and mobile-broadband-provider-info but something else?
Offline
#13 2022-04-19 13:17:15
- Lone_Wolf
- Member
- From: Netherlands, Europe
- Registered: 2005-10-04
- Posts: 11,919
Re: no IPv6 with ModemManager/NetworkManager
It looks that way, but It's still a bit early to conclude it .
Since there's now a known good and a a known bad point, it's possible to use bisection technicques to narrow down causes further.
Please check which date your last pacman -Syu before march 15 was .
Then use https://wiki.archlinux.org/title/Arch_L … cific_date to restore your system to the same state it had on march 15.
If ipv6-wwan fails in the restored state, there has to be an external cause.
In case it still works, later system states will need to be checked.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
(A works at time B) && (time C > time B ) ≠ (A works at time C)
Offline
#14 2022-04-24 14:15:11
- lamaral
- Member
- Registered: 2022-04-24
- Posts: 3
Re: no IPv6 with ModemManager/NetworkManager
I encountered this issue mid March and dug into it. It was caused by a bug in NetworkManager that has been fixed about 3 weeks ago, but haven't been released on a non-dev tag yet.
https://gitlab.freedesktop.org/NetworkM … issues/944
https://gitlab.freedesktop.org/NetworkM … uests/1170
I temporarily fixed it on my install by downgrading the NetworkManager package.
Offline