You are not logged in.
Pages: 1
Topic closed
My laptop's ipv6 address keeps changing, between something like
2601:603:f7f:b234::7f1/128
and something like
2601:603:f7f:b234:d63b:4ff:fe7b:363/64
If i do a [inline]watch -n1 ip addr show[/inline], I see these two lines appearing and disappearing once in a while
inet6 2601:603:f7f:b234:d63b:4ff:fe7b:363/64 scope global dynamic mngtmpaddr noprefixroute
valid_lft 240291sec preferred_lft 240291sec
This is causing chrome to keep displaying [inline]err_network_changed[/inline] once in a while. How do I start debugging this and what might the cause be?
Offline
You disconnect from the network and lose the IP, why that is cannot be said from the IP.
A common reason is that you're running competing network managing services, output of
find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f
?
If that's not it, we'll likely have to see the system journal (sudo journalctl -b)
Could be because of NM scanning the network and https://wiki.archlinux.org/title/Networ … domization - but that's completely baseless speculation at this point.
Offline
Here's the output! How do I read this?
$ find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f
dbus-org.freedesktop.network1.service | system
dbus-org.freedesktop.resolve1.service | system
dirmngr.socket | sockets.target.wants
getty@tty1.service | getty.target.wants
gpg-agent-browser.socket | sockets.target.wants
gpg-agent-extra.socket | sockets.target.wants
gpg-agent.socket | sockets.target.wants
gpg-agent-ssh.socket | sockets.target.wants
lenovo_fix.service | multi-user.target.wants
p11-kit-server.socket | sockets.target.wants
pulseaudio.socket | sockets.target.wants
remote-fs.target | multi-user.target.wants
systemd-networkd.service | multi-user.target.wants
systemd-networkd.socket | sockets.target.wants
systemd-resolved.service | multi-user.target.wants
tlp.service | multi-user.target.wants
wpa_supplicant@wlp2s0.service | multi-user.target.wants
$
Offline
You're using only systemd-networkd and wpa_supplicant (which will likely be the required carrier service since systemd-network doesn't establish wireless carriers itself)
To be sure: what is "lenovo_fix"?
tlp might be an issue (ie. your wifi chip takes a nap and loses the connection)
There's no obvious issue w/ your services, so let's have a look at the journal.
Offline
I'm using throttled (lenovo_fix) according to https://wiki.archlinux.org/title/Lenovo … ing_issues
Here's the last 512 lines of journalctl -b: http://ix.io/3weV
Thank you!
Offline
Seems the network environment, this is probably not a bug on your system
Aug 16 23:17:07 ackerleytng-x1c6 kernel: wlp2s0: deauthenticated from 98:da:c4:83:1b:e4 (Reason: 5=DISASSOC_AP_BUSY)
Aug 16 23:17:07 ackerleytng-x1c6 systemd-networkd[252]: wlp2s0: DHCP lease lost
Aug 16 23:17:07 ackerleytng-x1c6 wpa_supplicant[517]: wlp2s0: CTRL-EVENT-DISCONNECTED bssid=98:da:c4:83:1b:e4 reason=5
You get kicked from the 5GHz "A&W" AP…
Aug 16 23:17:09 ackerleytng-x1c6 wpa_supplicant[517]: wlp2s0: CTRL-EVENT-CONNECTED - Connection to 98:da:c4:83:1b:e5 completed [id=0 id_str=]
And connect to the 2.4GHz "A&W" AP…
Aug 16 23:17:17 ackerleytng-x1c6 kernel: wlp2s0: deauthenticated from 98:da:c4:83:1b:e5 (Reason: 5=DISASSOC_AP_BUSY)
8 seconds later it also kicks you…
Aug 16 23:17:19 ackerleytng-x1c6 wpa_supplicant[517]: wlp2s0: CTRL-EVENT-AUTH-REJECT 98:da:c4:83:1b:e5 auth_type=0 auth_transaction=2 status_code=17
And tells you to fuck off when you try to re-connect…
Aug 16 23:17:22 ackerleytng-x1c6 wpa_supplicant[517]: wlp2s0: CTRL-EVENT-CONNECTED - Connection to fe:ec:da:82:2e:11 completed [id=8 id_str=]
So you resort to the 5GHz "CityScape Guest" AP…
Aug 16 23:17:37 ackerleytng-x1c6 wpa_supplicant[517]: wlp2s0: CTRL-EVENT-BEACON-LOSS
Aug 16 23:17:37 ackerleytng-x1c6 systemd-networkd[252]: wlp2s0: Lost carrier
Aug 16 23:17:37 ackerleytng-x1c6 systemd-networkd[252]: wlp2s0: DHCP lease lost
Aug 16 23:17:37 ackerleytng-x1c6 wpa_supplicant[517]: wlp2s0: CTRL-EVENT-DISCONNECTED bssid=fe:ec:da:82:2e:11 reason=4 locally_generated=1
But that signal isn't strong enough (I guess - or you moved out of range)…
Aug 16 23:17:37 ackerleytng-x1c6 wpa_supplicant[517]: wlp2s0: CTRL-EVENT-AUTH-REJECT 98:da:c4:83:1b:e5 auth_type=0 auth_transaction=2 status_code=17
So you ask the 2.4GHz "A&W" AP to once more tell you to get lost…
Aug 16 23:17:42 ackerleytng-x1c6 wpa_supplicant[517]: wlp2s0: CTRL-EVENT-CONNECTED - Connection to fe:ec:da:81:2e:11 completed [id=8 id_str=]
So you move over to the 2.4GHz "CityScape Guest" AP…
Aug 16 23:17:55 ackerleytng-x1c6 sudo[95852]: ackerleytng : TTY=pts/7 ; PWD=/home/ackerleytng/downloads ; USER=root ; COMMAND=/usr/bin/systemctl restart wpa_supplicant@wlp2s0.service
You panic and restart wpa_supplicant…
Aug 16 23:17:55 ackerleytng-x1c6 wpa_supplicant[517]: wlp2s0: CTRL-EVENT-DISCONNECTED bssid=fe:ec:da:81:2e:11 reason=3 locally_generated=1
What opts you out of the 2.4GHz "CityScape Guest" AP…
Aug 16 23:17:57 ackerleytng-x1c6 wpa_supplicant[95856]: wlp2s0: SME: Trying to authenticate with 98:da:c4:83:1b:e5 (SSID='A&W' freq=2462 MHz)
Aug 16 23:17:57 ackerleytng-x1c6 kernel: wlp2s0: authenticate with 98:da:c4:83:1b:e5
Aug 16 23:17:57 ackerleytng-x1c6 kernel: wlp2s0: send auth to 98:da:c4:83:1b:e5 (try 1/3)
Aug 16 23:17:57 ackerleytng-x1c6 wpa_supplicant[95856]: wlp2s0: CTRL-EVENT-AUTH-REJECT 98:da:c4:83:1b:e5 auth_type=0 auth_transaction=2 status_code=17
And once more the 2.4GHz "A&W" AP, at this time probably really pissed about the dingus who keeps knocking, tells you to GTFO ;-)
Aug 16 23:18:01 ackerleytng-x1c6 wpa_supplicant[95856]: wlp2s0: SME: Trying to authenticate with 98:da:c4:83:1b:e4 (SSID='A&W' freq=5180 MHz)
Aug 16 23:18:01 ackerleytng-x1c6 kernel: wlp2s0: authenticate with 98:da:c4:83:1b:e4
Aug 16 23:18:01 ackerleytng-x1c6 kernel: wlp2s0: send auth to 98:da:c4:83:1b:e4 (try 1/3)
Aug 16 23:18:01 ackerleytng-x1c6 wpa_supplicant[95856]: wlp2s0: CTRL-EVENT-AUTH-REJECT 98:da:c4:83:1b:e4 auth_type=0 auth_transaction=2 status_code=17
Aug 16 23:18:01 ackerleytng-x1c6 kernel: wlp2s0: 98:da:c4:83:1b:e4 denied authentication (status 17)
Aug 16 23:18:04 ackerleytng-x1c6 wpa_supplicant[95856]: wlp2s0: SME: Trying to authenticate with 98:da:c4:83:1b:e5 (SSID='A&W' freq=2462 MHz)
Aug 16 23:18:04 ackerleytng-x1c6 kernel: wlp2s0: authenticate with 98:da:c4:83:1b:e5
Aug 16 23:18:04 ackerleytng-x1c6 kernel: wlp2s0: send auth to 98:da:c4:83:1b:e5 (try 1/3)
Aug 16 23:18:04 ackerleytng-x1c6 wpa_supplicant[95856]: wlp2s0: CTRL-EVENT-AUTH-REJECT 98:da:c4:83:1b:e5 auth_type=0 auth_transaction=2 status_code=17
Aug 16 23:18:04 ackerleytng-x1c6 kernel: wlp2s0: 98:da:c4:83:1b:e5 denied authentication (status 17)
So you try the 5GHz "A&W" (which I assume at this point fetches the Baseball Bat from the basement) and the 2.4GHz "A&W" AP (which is only left crying) and they tell you that they're not interested in your religion…
Aug 16 23:18:07 ackerleytng-x1c6 wpa_supplicant[95856]: wlp2s0: CTRL-EVENT-CONNECTED - Connection to fe:ec:da:81:2e:11 completed [id=8 id_str=]
So back to the 2.4GHz "CityScape Guest"…
Aug 16 23:18:27 ackerleytng-x1c6 wpa_supplicant[95856]: wlp2s0: SME: Trying to authenticate with 98:da:c4:83:1b:e4 (SSID='A&W' freq=5180 MHz)
Until 10 seconds later you try the sexier 5GHz "A&W" AP again…
Aug 16 23:18:27 ackerleytng-x1c6 wpa_supplicant[95856]: wlp2s0: CTRL-EVENT-CONNECTED - Connection to 98:da:c4:83:1b:e4 completed [id=0 id_str=]
Who perhaps got dropped by her date, but anyway: this time, she lets you in. 3rd base.
So bottom line:
There're 4 APs in your range, the "A&W" APs look better, but are also picky - and I guess you're just not that handsome.
The 5GHz "CityScape Guest" AP is probably too far away - whether the 2.4GHz one would ultimately pan out to be the unsexy but stable relation cannot be told atm (because you keep running from her)
"Networks"…
Offline
I'm using an OpenWrt router, any suggestions on how I can start debugging this?
Offline
"CityScape" sounds like a public hotspot, is "A&W" your private router?
You probably configured some quota or it for some reason runs out of leases and kicks you - you'll have to look at the router logs.
Offline
Turns out that my router was sending out the SLAAC flag on IPv6 Router Advertisement (RA) messages, and upon receiving it, my laptop would obtain a new IPv6 address. Repeated obtaining of IPv6 addresses causes this behavior. To fix this, I switched off the "Enable SLAAC" flag in my router's RA settings, and it seems like now the IPv6 addresses are stable.
Offline
Turns out that my router was sending out the SLAAC flag on IPv6 Router Advertisement (RA) messages, and upon receiving it, my laptop would obtain a new IPv6 address. Repeated obtaining of IPv6 addresses causes this behavior. To fix this, I switched off the "Enable SLAAC" flag in my router's RA settings, and it seems like now the IPv6 addresses are stable.
I was running into the same issue and this solved my problem, thank you!
Offline
Seems to be the day for necrobumps. Please don't do that.
Closing.
Offline
Pages: 1
Topic closed