OPNsense Forum
Archive => 20.1 Legacy Series => Topic started by: walkerx on June 30, 2020, 01:40:35 pm
-
I've noticed when i get a ppoe disconnection with opnsense I don't always get my ipv6 addressing back until after I've rebooted opnsense.
Again this morning i lost ipv6 and access to my work vpn (but was able to connect via mobile data) - i rebooted opnsense a few times and also updated to the 20.1.7 from 20.1.? it was only about an hour have my connection had been up and running again that dhcpv6server started working again and handing out ipv6 and roughly the same time i saw ipv6 working on the lan.
Is there a way to record that you are not receiving an ipv6 on wan and when it came back on other than using external sites to check.
Also why do I always have to fully reboot the system to get ipv6 working again after there has been an outage with my connection through maintenance by isp or just disconnection of the ppoe.
-
To check your IPv6 WAN is working use the gateway monitor. In the v6 gateway set a target GUA address such as the bbc - 2001:41c1:4008::bbc:1 or 2001:41c1:4008::bbc:2 and enable the monitor. You'll see from the dashboard then if v6 is working.
Need to know what your logs say, dhcp6c may have been in it's 'long winded' state where the gaps between sending solicits just get longer and longer, but without looking at the logs I can't be sure.
-
I had the same issue and picking an external GUA based GW monitor does not help. After a net drop out, the only way to get ipv6 connectivity back was a reboot.
I finally had to switch to pfsense because of the stability issues of opnsense, and today I had another ISP issue. Went down for about 10 seconds and pfsense came right back up on both ipv4 and ipv6. Rock solid.
This would have required a reboot of opnsense. I am also able to use my gateway (ISP) which is using Link Local ping.
I don't think this is a dpinger issue, I think Link Local traffic to the ISP gateway is not being properly routed.
I think there is something broken in the ipv6 WAN client. It is not participating in the Router Solicitation/Router Announcement protocol. I posted in a different thread that Link Local traffic is not going out the WAN interface, and verified via package capture.
-
It's not the client, there is an issue with 'no route to host' using the link local address to the gateway, whether that be dpinger or just ping6, I've raised the issue in Github. The dhcp6c solicitations are being sent. There was an issue with gateway switching not recovering too, that's now been fixed and applying the patch or waiting for the next release will fix that.
-
Are we talking about a PD of size /64 which we don't handle?
Cheers,
Franco
-
No, as I said last week, there's no route to host for dpinger or ping6 to the gateway on link-local, wireshark shows nothing either.
-
Are you on IRC? New home Internet is up and running and has IPv6 to test against.
Cheers,
Franco
-
Yeah... I'll cu on IRC.
-
@marjohn56 - All my settings are configured as originally setup with your help, but i've just noticed a few times when Zen has gone down, I've had to contact them to reapply my static ipv6 but on others it's still applied but when testing to ipv6-test.com i was getting not supported - the dhcp server had stopped and wouldn't restart even though the pppoe connection had restarted.
both uptime robot and thinkbroadband showed the ipv6 down
Usually starting stopping the wan connection does not resolve the issue, but a reboot from the menu options does.
I also ensured to update the system on monday which was successful, but on checking the update packages it initially failed (i think this is due to ipv6) but another reboot finally resolved this and ipv6 reenabled and working
-
As Zen allow us to use statics that's what I use. I only use dhcp6 between my primary and test routers. It very rarely has an issue, on the odd occasion a pppoe reset will kill dpinger but I have a Monit action to bring that back up. Quite boring really, I rarely look at the primary router. :)
-
@franco - I'll be on IRC all afternoon. DCC me if you are available and I'll chat to you about this.
-
i just have it setup using all the instructions provided via you :) when i switched from sky and pfsense and got the qotom setup
I think only thing I have at moment is the DNS override enabled so uses Zen (but may reset this back to Google servers)
but yes i have noticed that sometimes i have to manually restart dpinger or dhcpd6 after loss of ppoe connection, but some those may have been related to zen not re-applying my statics after they have done maintenance.
-
Very easy to switch to statics, it simplifies a few things or makes them more complex depending how you look at. Anyhoo, Franco is on the case with the link-local issue so that'll get resolved.