Closed maxfield-allison closed 3 years ago
This is very strange and I honestly have no idea why it would be behaving this way. I don't use IPv6 but have you looked at the specific instructions in the readme related to IPv6 stuff?
I also ran into this issue. Have not had time to do some through debugging, so had to disable it for now. :shrug:
@maxfield-allison and @BradenM Have you guys had any luck with additional tests? It would be good to add more details for other people that might encounter similar issues with IPv6.
I haven't had time lately but I still fully intend to take a solid stab at everything once life calms down a bit.
I am using pfatt on 20.1, and I do have dhcp6 on the wan enabled. I have had exactly zero problems....
I'm about to update it to 20.7, since 20.1 is now EoL ( https://butt.holdings )
lol
@dkowis can you share your dhcpv6 client config?
I don't run dhcpv6 relay or otherwise, it does the track interface. This is the LAN configuration:
Here's the WAN configuration for dhcp6:
After updating and running healthchecks, installing the netmap kernel and redoing the script and instal, I'm happy to say that dhcpv6 is working and bypass is functioning as it should. I'm guessing something got twisted up when I updated to 20.7 and by redoing all of it manually in the CLI the script was able to function correctly once more.
When I enable DHCPv6 on the WAN interface, My IPv4 connection drops every 30 or so seconds. It eventually comes back up but the behavior persists. The WAN interface does not pull an IPv6 address. I'm using the opnatt script on OPNsense 20.1.7