No public ipv6 address after upgraded to 24.7

Started by heypppoe, July 26, 2024, 01:25:08 AM

Previous topic - Next topic
October 18, 2024, 01:06:24 PM #15 Last Edit: October 18, 2024, 01:26:32 PM by nghappiness
Quote from: franco on July 26, 2024, 07:44:55 PM
SLAAC address? On DHCPv6 mode? ;)


Upgraded to 24.7.6

WAN, IPv4 DHCP, IPv6 DHCP6

WAN Interface no longer receive a public IPv6 address as in the /128.


ixl1: flags=1008a43<UP,BROADCAST,RUNNING,ALLMULTI,SIMPLEX,MULTICAST,LOWER_UP> metric 0 mtu 1500
        description: WAN (wan)
        options=4800028<VLAN_MTU,JUMBO_MTU,HWSTATS,MEXTPG>
        ether 3c:<redux>
        inet 157.xx.xx.xx netmask 0xfffff800 broadcast 157.xx.255.255
        inet6 fe80::3efd:feff:<redux>:<redux>%ixl1 prefixlen 64 scopeid 0x2
        media: Ethernet autoselect (10Gbase-Twinax <full-duplex>)
        status: active
        nd6 options=23<PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL>

<29>1 2024-10-18T04:21:12-07:00 firewall.local dhcp6c 27808 - [meta sequenceId="299"] Sending Solicit
<29>1 2024-10-18T04:21:12-07:00 firewall.local dhcp6c 27808 - [meta sequenceId="300"] set client ID (len 14)
<29>1 2024-10-18T04:21:12-07:00 firewall.local dhcp6c 27808 - [meta sequenceId="301"] set identity association
<29>1 2024-10-18T04:21:12-07:00 firewall.local dhcp6c 27808 - [meta sequenceId="302"] set elapsed time (len 2)
<29>1 2024-10-18T04:21:12-07:00 firewall.local dhcp6c 27808 - [meta sequenceId="303"] set option request (len 4)
<29>1 2024-10-18T04:21:12-07:00 firewall.local dhcp6c 27808 - [meta sequenceId="304"] set IA_PD prefix
<29>1 2024-10-18T04:21:12-07:00 firewall.local dhcp6c 27808 - [meta sequenceId="305"] set IA_PD
<29>1 2024-10-18T04:21:12-07:00 firewall.local dhcp6c 27808 - [meta sequenceId="306"] send solicit to ff02::1:2%ixl1
<29>1 2024-10-18T04:21:12-07:00 firewall.local dhcp6c 27808 - [meta sequenceId="307"] reset a timer on ixl1, state=SOLICIT, timeo=5, retrans=32498
<29>1 2024-10-18T04:21:44-07:00 firewall.local dhcp6c 27808 - [meta sequenceId="308"] Sending Solicit
<29>1 2024-10-18T04:21:44-07:00 firewall.local dhcp6c 27808 - [meta sequenceId="309"] set client ID (len 14)
<29>1 2024-10-18T04:21:44-07:00 firewall.local dhcp6c 27808 - [meta sequenceId="310"] set identity association
<29>1 2024-10-18T04:21:44-07:00 firewall.local dhcp6c 27808 - [meta sequenceId="311"] set elapsed time (len 2)
<29>1 2024-10-18T04:21:44-07:00 firewall.local dhcp6c 27808 - [meta sequenceId="312"] set option request (len 4)
<29>1 2024-10-18T04:21:44-07:00 firewall.local dhcp6c 27808 - [meta sequenceId="313"] set IA_PD prefix
<29>1 2024-10-18T04:21:44-07:00 firewall.local dhcp6c 27808 - [meta sequenceId="314"] set IA_PD
<29>1 2024-10-18T04:21:44-07:00 firewall.local dhcp6c 27808 - [meta sequenceId="315"] send solicit to ff02::1:2%ixl1
<29>1 2024-10-18T04:21:44-07:00 firewall.local dhcp6c 27808 - [meta sequenceId="316"] reset a timer on ixl1, state=SOLICIT, timeo=6, retrans=67049


Under WAN interface (Have not make any changes to these setting since initial setup back in 24.6)

Use IPv4 connectivity : Not Checked
Prefix delegation size : 56
Request prefix only : Not Checked
Send prefix hint : Checked

October 18, 2024, 04:45:19 PM #16 Last Edit: January 03, 2025, 03:41:59 PM by abulafia
This starts to sound like my problem: https://forum.opnsense.org/index.php?topic=43322.0

To summarise the German discussion:

0. Dual stack FTTH with M-Net as ISP. Connection is established via IPv4 PPPoE, IPv6 via DHCPv6 using the IPv4 link.
1. Initially, an IPv6 prefix delegation is received (over PPPoE). Everything is nice.
2. After the initial timeout, DHCPv6 tries to renew/rebind but fails.
3. IPv6 connection is lost. Only a reboot helps.

It seems from my limited investigation that the renew/rebind packets never actually are sent via WAN to my ISP and therefore cannot renew/rebind the IPv6 PD.

Alternative Routers have no issues and keep their IPv6 connection (FritzBox, Openwrt).

EDIT & UPDATE: The issue (or at least one issue) in my case was upstream traffic shaping (FQ-Codel).  Turning that off enables DHCPv6 lease renew.

Quote from: Homenetworking on August 02, 2024, 04:12:30 PMSame here: IPv4 working fine, but not IPv6 after upgrade to 24.7.
Turned out that the upgrade somehow changed two options in the interface configuration:
  • Prefix delegation size: Should be 56, was set to 64
  • Request prefix only: Should be checked, was unchecked
After setting the correct delegation size and checking "request prefix only", IPv6 works again.

Making those two changes fixed it for me. Thanks!

I have AT&T fiber, and the upgrade broke my IPV6 connectivity similarly to others' descriptions.