You are not logged in.
Hi,
My IPv6 Setup works flawlessly on my windows machine and on Android and iOS devices. I am using NetworkManager on my laptop and I have this issue, where (only at home) IPv6 seems to stop working. I still have an IPv6 address, but
$ ping ipv6.google.com
ping: connect: The network can't be reached (translated from German)
This issue does not happen on any other IPv6 networks, which are SLAAC or DHCPv6-stateless - I tried both settings on my router but that won't change anything. IPv6 settings in NetworkManager are also identical.
I am at my wit's end, and I also don't know how to go about debugging this issue. Any help how to debug this problem is greatly appreciated.
Offline
IPv6 settings in NetworkManager are also identical.
I am at my wit's end, and I also don't know how to go about debugging this issue.
Perhaps you could share some of those configuration details, otherwise we're just stabbing in the dark.
Are you familiar with our Forum Rules, and How To Ask Questions The Smart Way?
BlueHackers // fscanary // resticctl
Offline
Current NetworkManager configs are:
/etc/NetworkManager/system-connections # cat Interdimensional\ Cable.nmconnection
[connection]
id=Interdimensional Cable
uuid=2b9bbc21-df67-4589-ac6c-7ec6c8356b9a
type=wifi
interface-name=wlp3s0
permissions=
timestamp=1597707869
[wifi]
mac-address-blacklist=
mode=infrastructure
seen-bssids=28:80:88:nn:nn:nn;28:80:88:mm:mm:mm;
ssid=Interdimensional Cable
[wifi-security]
key-mgmt=wpa-psk
psk=xxxxxxxxxxxxxxxxxx
[ipv4]
dns=1.1.1.1;8.8.8.8;
dns-search=
method=auto
[ipv6]
addr-gen-mode=stable-privacy
dns-search=
ip6-privacy=0
method=auto
[proxy]
/etc/NetworkManager/conf.d # cat dhcp-client.conf
#[main]
#dhcp=dhclient #disabled because it didn't change anything
Installed and picked my network in nm. I have not touched any other network settings from install, used NetworkManager from first boot.
Offline
I'm not sure exactly how NM works, but could it be a delay caused by the interval of RA's on your network? If NM doesn't send a RS when it connects, then you won't get an address until the next RA.
Are you familiar with our Forum Rules, and How To Ask Questions The Smart Way?
BlueHackers // fscanary // resticctl
Offline
When NM connects, I usually have an IPv6, it just stops working after a while.
Offline
When NM connects, I usually have an IPv6, it just stops working after a while.
I don't use NM (dhcpcd), occasionally I'll get the same thing. A look thru the journal found a dhcpcd entry:
Aug 13 19:00:22 Jammin1 dhcpcd[1362920]: eth0: part of a Router Advertisement expired
Restarting dhcpcd works for awhile, then the above message again.
I don't know why, but the issue started with an ISP (Cox) reboot of my cable modem around the same time frame (WAN IPv4 address changed, IPv6 /64 didn't). Again, I don't know why, but my router doesn't particularly like when Cox does this.
A reboot of the router cleared the issue.
Eenie meenie, chili beanie, the spirits are about to speak -- Bullwinkle J. Moose
It's a big club...and you ain't in it -- George Carlin
Registered Linux user #149839
perl -e 'print$i=pack(c5,(41*2),sqrt(7056),(unpack(c,H)-2),oct(115),10); '
Offline