"
After upgrading to 26.1 I lost my IPv6 prefix. My ISP is Google Fiber, and they generally do IPv6 the right way, with DHCPv6 PD, and give out a /56 prefix. Worked fine with previous OPNSense versions. With tcpdump I can see some DHCPv6 activity:
I know there are a lot of changes with regards to IPv6 in this release. I began clicking around with the new options, trying out various permutations, like Identity Assocation and Track Interface (legacy). But it seems that things never progress that far, because my WAN interface never seems to get a IPv6 address or a prefix to delegate to the LAN interfaces. I did convert my firewall rules to the new format and deleted the legacy rules. Just to see if the new firewall config was causing issues I added a rule to allow inbound UDP 546 with no effect.
I'm posting some screenshots of my current config. Will be happy to provide more info and file a bug report if necessary once I learn more about what's going on. Thank you.
Code Select
16:46:46.740180 IP6 fe80::3eec:efff:fe27:ea7e.546 > ff02::1:2.547: dhcp6 solicit
16:46:46.742118 IP6 fe80::1.547 > fe80::3eec:efff:fe27:ea7e.546: dhcp6 advertise
16:46:47.740534 IP6 fe80::3eec:efff:fe27:ea7e.546 > ff02::1:2.547: dhcp6 request
16:46:47.742462 IP6 fe80::1.547 > fe80::3eec:efff:fe27:ea7e.546: dhcp6 reply
16:46:57.892093 IP6 fe80::3eec:efff:fe27:ea7e.546 > ff02::1:2.547: dhcp6 solicit
16:46:58.970018 IP6 fe80::3eec:efff:fe27:ea7e.546 > ff02::1:2.547: dhcp6 solicit
16:47:01.022492 IP6 fe80::3eec:efff:fe27:ea7e.546 > ff02::1:2.547: dhcp6 solicit
16:47:04.989532 IP6 fe80::3eec:efff:fe27:ea7e.546 > ff02::1:2.547: dhcp6 solicit
16:47:13.057771 IP6 fe80::3eec:efff:fe27:ea7e.546 > ff02::1:2.547: dhcp6 solicit
16:47:28.683178 IP6 fe80::3eec:efff:fe27:ea7e.546 > ff02::1:2.547: dhcp6 solicit
16:48:01.233762 IP6 fe80::3eec:efff:fe27:ea7e.546 > ff02::1:2.547: dhcp6 solicitI know there are a lot of changes with regards to IPv6 in this release. I began clicking around with the new options, trying out various permutations, like Identity Assocation and Track Interface (legacy). But it seems that things never progress that far, because my WAN interface never seems to get a IPv6 address or a prefix to delegate to the LAN interfaces. I did convert my firewall rules to the new format and deleted the legacy rules. Just to see if the new firewall config was causing issues I added a rule to allow inbound UDP 546 with no effect.
I'm posting some screenshots of my current config. Will be happy to provide more info and file a bug report if necessary once I learn more about what's going on. Thank you.
