IPv6 PD Address not being assigned

Installing and Using OpenWrt Network and Wireless Configuration
21

Unfortunately no improvement here, except one less LLA error.

[6 Jul 2026, 17:59:55 UTC] daemon.notice: netifd: Interface 'wan6' is enabled
[6 Jul 2026, 17:59:55 UTC] daemon.notice: netifd: Interface 'wan6' has link connectivity
[6 Jul 2026, 17:59:55 UTC] daemon.notice: netifd: Interface 'wan6' is setting up now
[6 Jul 2026, 17:59:55 UTC] daemon.notice: netifd: wan6 (3204): Failed to send RS (Address not available)
[6 Jul 2026, 17:59:55 UTC] daemon.notice: netifd: wan6 (3204): wan: error connecting LLA socket
[6 Jul 2026, 17:59:55 UTC] daemon.notice: netifd: wan6 (3204): Failed to send SOLICIT message to ff02::1:2 (Address not available)

config interface 'wan'
        option proto 'dhcp'
        option device 'wan'
        option hostname '*'
        option multipath 'off'

config interface 'wan6'
        option proto 'dhcpv6'
        option device '@wan'
        option reqaddress 'try'
        option reqprefix '0:1'
        option norelease '1'
        option multipath 'off'
22

Perhaps remove that

23

Apologies - that was a typo when writing up the post, have edited to reflect real config.

24

Regarding PD ipv6.
This is my 2 cents and I could be completely wrong.

I have tested to remove DUID and reboot and not get any ipv6 from my isp.
Also generated new duid stil no ipv6

It's normally give PD /56 and it's working. Doesn't matter what i did no ipv6.
Cloned my WAN macaddress did the trick and get ipv6.
Seems isp have som difficulty to lease/relese ipv6

25

The devs ate working on it there are actual at least 2 problems one is about the prefix delegation not working and the other about the dhcp server not being enabled by default see Policy-Based-Routing (pbr) package discussion - #2885 by egc

26

Same thing happened to my router after upgrading to 25.12.5 (from .4). My "Request IPv6-prefix" was set to 48. I set it to "Automatic" and I don't recall what "IPv6 assignment length" was set to originally but I set that to 64. Applied it all and the router received an IPv6 address again.

27

After getting no ipv6 with 25.12 or 24.10 or 23.5.... I thought I was dead in the water. But on a lark I went all the way back to 17.01.7.

Lo and behold, ipv6 came up just fine. Interestingly enough, the system log still has the same error messages:

Thu Jun 20 10:53:59 2019 daemon.notice netifd: Network device 'eth0' link is up
Thu Jun 20 10:53:59 2019 daemon.notice netifd: Interface 'wan' has link connectivity 
Thu Jun 20 10:53:59 2019 daemon.notice netifd: Interface 'wan' is setting up now
Thu Jun 20 10:53:59 2019 daemon.notice netifd: Interface 'wan6' has link connectivity 
Thu Jun 20 10:53:59 2019 daemon.notice netifd: Interface 'wan6' is setting up now
Thu Jun 20 10:53:59 2019 daemon.notice netifd: wan (883): udhcpc: started, v1.25.1
Thu Jun 20 10:53:59 2019 daemon.info odhcpd[789]: Using a RA lifetime of 0 seconds on br-lan
Thu Jun 20 10:53:59 2019 daemon.notice odhcpd[789]: Failed to send to fe80::cdd:cd54:2291:6231%br-lan (Address not available)
Thu Jun 20 10:53:59 2019 user.notice firewall: Reloading firewall due to ifup of lan (br-lan)
Thu Jun 20 10:54:00 2019 daemon.notice netifd: Interface 'wan' is now up
Thu Jun 20 10:54:00 2019 daemon.err odhcp6c[882]: Failed to send DHCPV6 message to ff02::1:2 (Address not available)

But then later on in the log there are some good dhcpv6 messages:

Thu Jun 20 10:54:05 2019 daemon.notice odhcpd[789]: Got DHCPv6 request
Thu Jun 20 10:54:05 2019 daemon.warn odhcpd[789]: DHCPV6 SOLICIT IA_NA from 000300013498b57d209b on br-lan: ok fd47:14ca:8670::6eb/128 
Thu Jun 20 10:54:05 2019 daemon.warn odhcpd[789]: DHCPV6 SOLICIT IA_PD from 000300013498b57d209b on br-lan: ok fd47:14ca:8670:4::/62

So for the time being I guess I'm going to (sadly) stay waaaaay in the past.

28

For everyone still having trouble getting IPv6 PD, there was an update to odhcp6c and related packages that fixed the DDUI part of the request.

You can run Attended Sysupgrade or owut and request an updated 25.12.5 build and install it over your existing installations.

EDIT: typo.

29

odhcp6c is the name of package which requires upgrade.

30

Sorry, that's the one. Typo.

Thanks for the correction.

31

Could you please edit your original post? Thanks!

32

I'm running 25.12.4 and have been delaying installing 25.12.5 because of this issue. Are you saying that the issue is fixed, and all I have to do is wait a day or two for the fix to propagate to the CDNs, then update to 25.12.5? Or are you saying that I have to update to 25.12.5, then use apk to install the latest odhcp6c version?

33

You can upgrade right away with owut or Attended Sysupgrade because it'll generate an image with all the packages updated.

If it doesn't work, you could just flash 25.12.4 while keeping settings and you won't lose a thing.

But yeah, the odhcp6c package is updated with the fix. Although I managed to get PD with the old package just by regenereating the default DDUID on Network > Interfaces > Global Network options. Also, turning off the modem for 3 to 5 minutes.

34

Thanks for the owut hint - this fixed my combination of 25.12.5 router and AP where I couldn't access an internal device on IPv6 when connected via the AP, but could connected via the router.

owuted both of them up to 25.12.5 again to pick up the updated odhcpv6 and around 30 other packges.

happy daze

35

"owuted", I like this verb. @efahl will also like this :wink:

36

Still getting these errors with the upgraded odhcp6c:

[11 Jul 2026, 04:06:16 UTC] daemon.notice: netifd: Interface 'wan6' is enabled
[11 Jul 2026, 04:06:16 UTC] daemon.notice: netifd: Interface 'wan6' has link connectivity
[11 Jul 2026, 04:06:16 UTC] daemon.notice: netifd: Interface 'wan6' is setting up now
[11 Jul 2026, 04:06:16 UTC] daemon.notice: netifd: wan6 (3350): Failed to send RS (Address not available)
[11 Jul 2026, 04:06:16 UTC] daemon.notice: netifd: wan6 (3350): wan: error connecting LLA socket

with this config:

# cat /etc/config/network 

config interface 'loopback'
        option device 'lo'
        option proto 'static'
        list ipaddr '127.0.0.1/8'

config globals 'globals'
        option ula_prefix 'fd2a:xxxx:yyyy::/48'
        option packet_steering '2'
        option steering_flows '128'
        option dhcp_default_duid '0004f7[...]341c'

config device
        option type '8021q'
        option ifname 'eth0'
        option vid '7'
        option name 'wan'

config interface 'wan'
        option proto 'dhcp'
        option device 'wan'
        option hostname '*'
        option multipath 'off'

config interface 'wan6'
        option proto 'dhcpv6'
        option device '@wan'
        option reqaddress 'try'
        option reqprefix 'auto'
        option norelease '1'
        option multipath 'off'

Unless anyone suspects any further issues on my end, I'm going to contact the ISP next week and see if they can provide any insight, considering the DUID change.
Thanks.