Whenever I set the LAN IPv6 Configuration Type to Track Interface I get the following log errors.
2023-03-25T16:29:59-07:00 Error configd.py [8652173a-ab02-4b61-b2bd-158d148350a9] returned exit status 1
2023-03-25T16:29:59-07:00 Notice configd.py [8652173a-ab02-4b61-b2bd-158d148350a9] update IPv6 prefixes
I have the prefix set to 56, which is what the ISP told me. I also tried 64 and 60 and enabling the Request only an IPv6 prefix and prefix hit.
Is there another setting I need to do, or is this maybe caused by the ISP?
By the way, I do get an IPv6 address on the clients.
Quote from: dcol on March 26, 2023, 12:48:24 AM
I do get an IPv6 address on the clients.
I would say there is no issue 8)
Can the clients reach IPv6 resources? Browse http://www.kame.net and check that the turtle swims
Bart...
They change something since 23.1 my friend dont get any prefix from provider.
But no one do anything about it i think, because there ar so many ways to deligate
prefix it depend on what equipment the provider have, so for some it works the rest not
I dont think there is so many that use IPV6 so that could be why it dont have any priority
to be fixed.
//P
Quote from: YipieKaie on March 27, 2023, 12:31:06 AM
They change something since 23.1 my friend dont get any prefix from provider.
But no one do anything about it i think, because there ar so many ways to deligate
prefix it depend on what equipment the provider have, so for some it works the rest not
I dont think there is so many that use IPV6 so that could be why it dont have any priority
to be fixed.
I am having the same issue.
I am no longer able to get a prefix and an IPv6 address on the WAN port with 23.1, and browsing the forum did not seem to provide any meaningful solution to the issue, sadly.
It's been a very frustrating experience ever since my ISP turned off 6RD, which used to work perfectly.
With dual stack on OPNsense I have been having only issues since the 6RD switch off.
Bye, Luca
Quick update, IPv6 seems to be working now that I have performed what is mentioned in this message:
https://forum.opnsense.org/index.php?topic=32263.msg160190#msg160190
Basically running a script from the GUI fixed things for me, at least for the time being.
The simple execution of
/usr/local/etc/rc.configure_interface wan
fixed things. Go figure!
Bye, Luca