Ipv6 available on wan, but not delegated to clients on lan.

[MamyPoko]

Hello.
my router assigned ipv6 in wan interface, but the clients on lan does not receive the address.

in system log>ipv6 it shows my /64 ipv6 in wan. but its not delegated to lan and stays /0.

The IPv6 is valid and routed, work fine inside router. I can ping and wget no problem.

It's all blank on ipv6 setting page.

Any idea of what's going on here?
(AC67U, 386.3_2)

 

[heysoundude]

what's an AC-67?
You're running Merlin on unsupported hardware...I'd guess that's probably the main factor.

 

[MamyPoko]

what's an AC-67?
You're running Merlin on unsupported hardware...I'd guess that's probably the main factor.

AC-67U is also known as RT-AC1900, marketed and sold primarily as bundle of mesh cluster. It is supported model.

It's basically refreshed version of otherwise identical AC68U hadware but with higher cpu clock, built inside horizontal chassis (instead of 68U's vertical chassis).
I think it's quite rare outside Asian market.

 

[dave14305]

Try enabling more debugging of odhcp6c and reboot and check the syslog.

nvram set ipv6_debug=1
nvram commit
service reboot

Also look at the interfaces with this command (before and after the reboot)

ip -6 addr

 

[MamyPoko]

Try enabling more debugging of odhcp6c and reboot and check the syslog.

nvram set ipv6_debug=1
nvram commit
service reboot

Also look at the interfaces with this command (before and after the reboot)

ip -6 addr

tried, but im not sure if im getting any meaningful info from the log here

admin@RT-AC67U-9CF8 /jffs> cat syslog.log | grep odhcp6c
May  5 13:05:19 odhcp6c[1333]: (re)starting transaction on ppp0
May  5 13:05:20 odhcp6c[1333]: Starting SOLICIT transaction (timeout 4294967295s, max rc 0)
May  5 13:05:21 odhcp6c[1333]: Got a valid reply after 1075ms
May  5 13:05:23 odhcp6c[1333]: Got a valid reply after 3174ms
Dec  3 03:45:23 odhcp6c[1333]: Got a valid reply after 7527ms
Dec  3 03:45:32 odhcp6c[1333]: Got a valid reply after 16081ms
Dec  3 03:45:49 odhcp6c[1333]: Got a valid reply after 32851ms
Dec  3 03:46:22 odhcp6c[1333]: Got a valid reply after 66213ms
Dec  3 03:47:26 odhcp6c[1333]: Got a valid reply after 130593ms
Dec  3 03:48:12 odhcp6c[3053]: (re)starting transaction on ppp0
Dec  3 03:48:13 odhcp6c[3053]: Starting SOLICIT transaction (timeout 4294967295s, max rc 0)
Dec  3 03:48:13 odhcp6c[3053]: Got a valid reply after 50ms
Dec  3 03:48:14 odhcp6c[3053]: Got a valid reply after 1053ms
Dec  3 03:48:16 odhcp6c[3053]: Got a valid reply after 3163ms
Dec  3 03:48:20 odhcp6c[3053]: Got a valid reply after 7282ms
Dec  3 03:48:28 odhcp6c[3053]: Got a valid reply after 15153ms

(as usual), only ppp0 is getting global ipv6

13: ppp0: <POINTOPOINT,MULTICAST,UP,LOWER_UP> mtu 1492 qlen 3
    inet6 2404:160:188:629f:55fe:352f:6200:3ac0/64 scope global dynamic
       valid_lft 258827sec preferred_lft 172427sec
    inet6 fe80::55fe:352f:6200:3ac0/10 scope link
       valid_lft forever preferred_lft forever

 

[dave14305]

tried, but im not sure if im getting any meaningful info from the log here

admin@RT-AC67U-9CF8 /jffs> cat syslog.log | grep odhcp6c
May  5 13:05:19 odhcp6c[1333]: (re)starting transaction on ppp0
May  5 13:05:20 odhcp6c[1333]: Starting SOLICIT transaction (timeout 4294967295s, max rc 0)
May  5 13:05:21 odhcp6c[1333]: Got a valid reply after 1075ms
May  5 13:05:23 odhcp6c[1333]: Got a valid reply after 3174ms
Dec  3 03:45:23 odhcp6c[1333]: Got a valid reply after 7527ms
Dec  3 03:45:32 odhcp6c[1333]: Got a valid reply after 16081ms
Dec  3 03:45:49 odhcp6c[1333]: Got a valid reply after 32851ms
Dec  3 03:46:22 odhcp6c[1333]: Got a valid reply after 66213ms
Dec  3 03:47:26 odhcp6c[1333]: Got a valid reply after 130593ms
Dec  3 03:48:12 odhcp6c[3053]: (re)starting transaction on ppp0
Dec  3 03:48:13 odhcp6c[3053]: Starting SOLICIT transaction (timeout 4294967295s, max rc 0)
Dec  3 03:48:13 odhcp6c[3053]: Got a valid reply after 50ms
Dec  3 03:48:14 odhcp6c[3053]: Got a valid reply after 1053ms
Dec  3 03:48:16 odhcp6c[3053]: Got a valid reply after 3163ms
Dec  3 03:48:20 odhcp6c[3053]: Got a valid reply after 7282ms
Dec  3 03:48:28 odhcp6c[3053]: Got a valid reply after 15153ms

as usual, (only) ppp0 is getting global ipv6

13: ppp0: <POINTOPOINT,MULTICAST,UP,LOWER_UP> mtu 1492 qlen 3
    inet6 2404:160:188:629f:55fe:352f:6200:3ac0/64 scope global dynamic
       valid_lft 258827sec preferred_lft 172427sec
    inet6 fe80::55fe:352f:6200:3ac0/10 scope link
       valid_lft forever preferred_lft forever

I think you need to talk to the ISP to understand if they actually will delegate you a prefix. I barely know what I’m talking about, but I would always get a /128 WAN address and a /64 prefix delegated for LAN, using Comcast as my ISP in the US.

Also check the syslog for “dhcp6 client” messages.

 

[MamyPoko]

I think you need to talk to the ISP to understand if they actually will delegate you a prefix. I barely know what I’m talking about, but I would always get a /128 WAN address and a /64 prefix delegated for LAN, using Comcast as my ISP in the US.

Also check the syslog for “dhcp6 client” messages.

there are no “dhcp6 client” entry in the log.

There are no problem on prefix from ISP, I think. SLAAC is pretty much national standard here. /64 prefix for home users. Business customers gets /56.
I haven't contacted my ISP to find out whether the problem is originated from them somehow, (I'm not fully understand the entire process of IPv6 addressing) but I'm assuming if the router gets a valid prefix on wan, it's the router's responsibility to advertise it on lan.

 

[heysoundude]

AC-67U is also known as RT-AC1900, marketed and sold primarily as bundle of mesh cluster. It is supported model.

It's basically refreshed version of otherwise identical AC68U hadware but with higher cpu clock, built inside horizontal chassis (instead of 68U's vertical chassis).
I think it's quite rare outside Asian market.

Ok, I stand educated/corrected. I went looking on Merlin's "supported hardware" list and didn't see the model designator you used. The AC1900 I know.

 

[heysoundude]

there are no “dhcp6 client” entry in the log.

There are no problem on prefix from ISP, I think. SLAAC is pretty much national standard here. /64 prefix for home users. Business customers gets /56.
I haven't contacted my ISP to find out whether the problem is originated from them somehow, (I'm not fully understand the entire process of IPv6 addressing) but I'm assuming if the router gets a valid prefix on wan, it's the router's responsibility to advertise it on lan.

This will help you: https://ipv6.he.net/certification/
the login/pwd you make there also give you access to their tunnelbroker.net DDNS service (easy set-up included in both asus and merlin's firmware) where you can claim your own /48
All of this is free of charges/fees. the first 2-3 levels of study took me maybe 2 hours.