Double NAT, IA_PD

[03.05.2026, 16:25:05 MESZ] daemon.notice: netifd: wan6 (32459): Server returned IA_PD status 'Not On Link (This address is not on link)'

This info I recieve in the system log. As I understand, this is caused, when the ipv6 prefix is not configured correctly. In the settings this option is set to 'automatic'. I try to change this step by step. No change, still get info in the logs.

In the interfaces section I can read: IPv6: 2a02:2455:XXXX:9900:9683:XXXX:fed1:53d7 /64
xxxx by me for cover.

There are no issues with internet access and everything works fine. I just experienced, that I'm not able to log in to my ISP router anymore. I got the right password, but it wont load the backend. And I think this has something to do with the double natting issue with the IA_PD.

Did I understand correctly? There are some other info messages too. The message above appears 3-4 times a second. Can anyone please explain what this is and why this appears in the logs?

I read anywhere, that I can probably fix this when I put the ISP router into bridged mode. But my ISP dont have such option. I can only set up a DMZ, but no bridge-mode or anything. Nevertheless, I cannot login to change something anyways. :slight_smile:

When I'm in the ISP Network via wifi I think I should login, but it seems that something is fundamentally changed with the ISP router. Even direct via ethernetport I'm not able to login anymore.

which isp, which technology and which isp router? Maybe you could try rebooting the isp router?

Hi!
This is PYUR (Telecolumbus AG / Germany).
Its a modern router with ipv4+6 dual-use with broadband cable / DSL.

I rebooted.

There were 2 wifis set up with the ISP router: 2,4 Ghz and for 5 Ghz. Now, after rebooting, the ISP router is not giving any IPv4 adresses, only IPv6. Under both SSIDs... Wtf?

That means, the flint2 is not recieving a IPv4 adress for the wan interface. The network behind the flint2 is down. :confused:

I cannot even access the ISP routers IPv4 adress to get to the login mask under 192.168.40.1.

But I can access the internet. Just ping any site is not possible.

To be clear: Im now in the wifi from the ISP router. The flint2-network is not functioning at the moment.

I'm rebooting ISP router again.

The ISP router is still giving IPv6 adresses only.

Some internetsites are working, some wont. I cannot even think of a solution to this without resetting the ISP router. Its lost its ipv4 functionality, it seems! xD

Ah, cable/docsis... try logging into the cable model using 192.168.100.1 as destination address, that should reveal some low level DOCSIS statistics, even though I assume that the docsis level is fine, and you ISP simply has its provisioning especially for IPv4 in a tangle...

Why that? Did you disable IPv6 in your internal network? If yes, why?

Hey,

After I rebooted the ISP router, it was not gonna assign any ipv4 adresses anymore. Only ipv6.
That means, the openwrt router will not recieve any IPv4 adresses for the wan interface. Only the wan6 interface is recieving an adress. Before that, everything seems to be good.

So, now I have a complete different problem that this one in the first post. :slight_smile:

Now the openwrtrouter is still logging:
[03.05.2026, 19:36:18 MESZ] daemon.notice: netifd: wan6 (7520): Server returned IA_PD status 'Not On Link (This address is not on link)'
but I can only access some internetsites, not all. And ping is not working completely from within the ISP router ssids.

This happens on both ISP ssids. 2,4 and 5 GHz.

Rebooting is not helping. ISP router still assign IPv6 only! For the initial setup see the first post, I added a scheme.

Could it be, that the ISP Router lost its dns settings somehow? Due to my individual dns settings from the openwrt router? Edit: no, this is crap.

I guess there is no other way to reset the ISP router (in the hope, that I never ever must write down the letters ISP router again!)

No, seriously, I would like to know what causes the ability loss of serving ipv4 adresses.

Edit, possible issues: Sometimes this can be caused by an incorrect system time. If your system time is too far off, you will not be leased an IPv4 by DHCP -- only an IPv6. Does it makes sense here? The openwrt router has indeed a dfferent systemtime.

you cannot add routers for additional IPv6 subnets if your ISP hands out a /64. The ISP would need to issue e.g a /62, /60 or /56, to be able to do this.

  • You could install NAT64, but I would strongly advise to not go down that rabbit hole.
  • You can also search this forum for OpenWRT ipv6 relay mode. Relay mode allows you to forward a /64 WAN prefix to a single (1) LAN interface.

can happen, if you reuse the same subnet both on the LAN side of your cable router and on the LAN side of your OpenWRT router.

The bridge option is usually in the customer online web portal, not in the admin UI of the cable modem.

No, I'm using different ones.
For ISP router: 192.168.40.1
For wan interface: 192.168.40.xx
For lan interface: 192.168.100.1/24

Ok, I think I reset the ISP router and then try to figure out this ipv6 issue from the logs first.

Edit:
I just let the ISP router on 192.168.0.1 and the wan without any fixed IP. Its working for now. I try a bit with the wan setting regarding the preset until the logs stop. If you have a specific setting in mind (for example hows possible that the router "forget" about ipv4 suddenly), please head back to me, its highly appreciated! :slight_smile:

Thank you both!

Ok, theres a solution to this case, when the ISP sends the prefix /64 (like mine do). Go to EDIT in the interfaces section of wan6.

And now the log is ... silent. Ahhhh... phew! :face_holding_back_tears: