IPv6 Config with VLAN WAN

[rlh]

Wondering if anyone has been able to get IPv6 working using a WAN connection that utilises VLAN? In my country, VLAN tagging with ID 10 is required on the WAN port, with the IP address set using DHCP? I have had a trawl through the forums here but was unable to find any configs that people had working!

My router is an AX82U running merlin 388.1 0-gnuton1.

Internet through IPv4 is working fantastically however I would like to try and get IPv6 working. Using connection type [Native] with DHCP-PD enabled and a prefix length of 56 my router is given an IPv6 address and by logging in through SSH I am able to ping IPv6 addresses no problem. Clients are given IPv6 addresses through DHCP (I get one on my laptop beginning fe80:, and two beginning 2404: ) however they cannot ping or communicate with any IPv6 addresses.

An example traceroute6 from the router:

traceroute to google.com (2404:6800:4006:80b::200e), 30 hops max, 16 byte packets
1 default-rdns.vocus.co.nz (2400:4800::30) 2.259 ms 4.637 ms 3.560 ms
2 2620:107:4008:6ff::2 (2620:107:4008:6ff::2) 45.152 ms 43.978 ms 43.633 ms
3 2001:4860:1:1::1510 (2001:4860:1:1::1510) 44.179 ms 42.878 ms 43.765 ms
4 2404:6800:80d8::1 (2404:6800:80d8::1) 44.624 ms 43.576 ms *
5 2001:4860:0:1::4240 (2001:4860:0:1::4240) 45.208 ms 46.208 ms 43.844 ms
6 2001:4860:0:1108::a (2001:4860:0:1108::a) 42.530 ms 42.833 ms 43.917 ms
7 2001:4860:0:1109::1 (2001:4860:0:1109::1) 44.165 ms 45.028 ms 44.155 ms
8 2001:4860:0:1::5f7 (2001:4860:0:1::5f7) 44.335 ms 43.839 ms 43.936 ms
9 syd09s17-in-x0e.1e100.net (2404:6800:4006:80b::200e) 43.204 ms 44.038 ms 43.749 ms

and from my laptop

traceroute6 to google.com (2404:6800:4006:813::200e), 64 hops max, 12 byte packets
1 my-router-name 2.998 ms 2.624 ms 2.869 ms
2 default-rdns.vocus.co.nz 27.566 ms 27.344 ms 27.731 ms
3 * *

The interface used for internet on the router is vlan10, I am wondering if this is the cause of the issue?

Any idea what is going on? I tried searching online but couldn't quite find anything that would help, aside from suggestions that it was a routing issue?

Cheers, any help would be much appreciated, this project is amazing aside from this small hiccup and I really appreciate the work you do!

 

[SomeWhereOverTheRainBow]

Wondering if anyone has been able to get IPv6 working using a WAN connection that utilises VLAN? In my country, VLAN tagging with ID 10 is required on the WAN port, with the IP address set using DHCP? I have had a trawl through the forums here but was unable to find any configs that people had working!

My router is an AX82U running merlin 388.1 0-gnuton1.

Internet through IPv4 is working fantastically however I would like to try and get IPv6 working. Using connection type [Native] with DHCP-PD enabled and a prefix length of 56 my router is given an IPv6 address and by logging in through SSH I am able to ping IPv6 addresses no problem. Clients are given IPv6 addresses through DHCP (I get one on my laptop beginning fe80:, and two beginning 2404: ) however they cannot ping or communicate with any IPv6 addresses.

An example traceroute6 from the router:

traceroute to google.com (2404:6800:4006:80b::200e), 30 hops max, 16 byte packets
1 default-rdns.vocus.co.nz (2400:4800::30) 2.259 ms 4.637 ms 3.560 ms
2 2620:107:4008:6ff::2 (2620:107:4008:6ff::2) 45.152 ms 43.978 ms 43.633 ms
3 2001:4860:1:1::1510 (2001:4860:1:1::1510) 44.179 ms 42.878 ms 43.765 ms
4 2404:6800:80d8::1 (2404:6800:80d8::1) 44.624 ms 43.576 ms *
5 2001:4860:0:1::4240 (2001:4860:0:1::4240) 45.208 ms 46.208 ms 43.844 ms
6 2001:4860:0:1108::a (2001:4860:0:1108::a) 42.530 ms 42.833 ms 43.917 ms
7 2001:4860:0:1109::1 (2001:4860:0:1109::1) 44.165 ms 45.028 ms 44.155 ms
8 2001:4860:0:1::5f7 (2001:4860:0:1::5f7) 44.335 ms 43.839 ms 43.936 ms
9 syd09s17-in-x0e.1e100.net (2404:6800:4006:80b::200e) 43.204 ms 44.038 ms 43.749 ms

and from my laptop

traceroute6 to google.com (2404:6800:4006:813::200e), 64 hops max, 12 byte packets
1 my-router-name 2.998 ms 2.624 ms 2.869 ms
2 default-rdns.vocus.co.nz 27.566 ms 27.344 ms 27.731 ms
3 * *

The interface used for internet on the router is vlan10, I am wondering if this is the cause of the issue?

Any idea what is going on? I tried searching online but couldn't quite find anything that would help, aside from suggestions that it was a routing issue?

Cheers, any help would be much appreciated, this project is amazing aside from this small hiccup and I really appreciate the work you do!

Please provide an screenshot of your ipv6 settings page. Basically show what options you have enabled. it could be something as simple as selecting the correct connection type, e.g. PPOE on the dhcp6 webpage.

 

[drinkingbird]

Wondering if anyone has been able to get IPv6 working using a WAN connection that utilises VLAN? In my country, VLAN tagging with ID 10 is required on the WAN port, with the IP address set using DHCP? I have had a trawl through the forums here but was unable to find any configs that people had working!

My router is an AX82U running merlin 388.1 0-gnuton1.

Internet through IPv4 is working fantastically however I would like to try and get IPv6 working. Using connection type [Native] with DHCP-PD enabled and a prefix length of 56 my router is given an IPv6 address and by logging in through SSH I am able to ping IPv6 addresses no problem. Clients are given IPv6 addresses through DHCP (I get one on my laptop beginning fe80:, and two beginning 2404: ) however they cannot ping or communicate with any IPv6 addresses.

An example traceroute6 from the router:

traceroute to google.com (2404:6800:4006:80b::200e), 30 hops max, 16 byte packets
1 default-rdns.vocus.co.nz (2400:4800::30) 2.259 ms 4.637 ms 3.560 ms
2 2620:107:4008:6ff::2 (2620:107:4008:6ff::2) 45.152 ms 43.978 ms 43.633 ms
3 2001:4860:1:1::1510 (2001:4860:1:1::1510) 44.179 ms 42.878 ms 43.765 ms
4 2404:6800:80d8::1 (2404:6800:80d8::1) 44.624 ms 43.576 ms *
5 2001:4860:0:1::4240 (2001:4860:0:1::4240) 45.208 ms 46.208 ms 43.844 ms
6 2001:4860:0:1108::a (2001:4860:0:1108::a) 42.530 ms 42.833 ms 43.917 ms
7 2001:4860:0:1109::1 (2001:4860:0:1109::1) 44.165 ms 45.028 ms 44.155 ms
8 2001:4860:0:1::5f7 (2001:4860:0:1::5f7) 44.335 ms 43.839 ms 43.936 ms
9 syd09s17-in-x0e.1e100.net (2404:6800:4006:80b::200e) 43.204 ms 44.038 ms 43.749 ms

and from my laptop

traceroute6 to google.com (2404:6800:4006:813::200e), 64 hops max, 12 byte packets
1 my-router-name 2.998 ms 2.624 ms 2.869 ms
2 default-rdns.vocus.co.nz 27.566 ms 27.344 ms 27.731 ms
3 * *

The interface used for internet on the router is vlan10, I am wondering if this is the cause of the issue?

Any idea what is going on? I tried searching online but couldn't quite find anything that would help, aside from suggestions that it was a routing issue?

Cheers, any help would be much appreciated, this project is amazing aside from this small hiccup and I really appreciate the work you do!

Is your WAN VLAN configured via the GUI IPTV tab or via a script?

 

[rlh]

Thanks for the quick responses! My ISP uses DHCP rather than PPPoE, and I believe it offers native IPv6, although their documentation for their implementation is much lacking. I used the Native setting for IPv6, which does provide the router with an IPv6 address as mentioned earlier.

I configured the VLAN using the GUI.
Screenshots attached for my config.

 

[drinkingbird]

Thanks for the quick responses! My ISP uses DHCP rather than PPPoE, and I believe it offers native IPv6, although their documentation for their implementation is much lacking. I used the Native setting for IPv6, which does provide the router with an IPv6 address as mentioned earlier.

I configured the VLAN using the GUI.
Screenshots attached for my config.

Generally looks ok. Your traceroutes imply that the ISP does not have a route for your LAN IPv6 (you can hit their first hop but nothing after that), which may mean they require passthrough mode in which your LAN uses the subnet they hand out directly rather than subnetting it. But you can try tweaking some settings with Native mode and see if anything changes. Unfortunately every ISP is different and if their documentation isn't good you may have to try and search for someone with the same ISP that has gotten it working.

It does appear that PD is working as you have gotten a /64 for your LAN (I'm assuming it is from the same /56 as the WAN). Have you tried turning on stateful configuration? May just be a matter of trial and error. Did you put in the 56 prefix length for the WAN or was that received automatically? I think /48 is typical but obviously there is no rule.

Be cautious though there are implications of the different modes and what can/can't be seen and accessed from the internet etc.

Can you also confirm there is no ISP router in the path? If there is, then you almost certainly will have to use passthrough.

Then of course there is the standard disclaimer - if you don't need IPv6 for one of the very few reasons people actually need it (such as your IPv4 is CGNAT and you want inbound connections or certain VPNs), you are putting yourself at some risk by enabling it no matter what mode you use. IPv6 is definitely not polished and fully ready for prime time on Asus or most home-oriented routers. It also requires an understanding of how it differs from IPv4 and how one of the "if all else fails" security measures (hide NAT) is no longer there, etc.

 

[SomeWhereOverTheRainBow]

Thanks for the quick responses! My ISP uses DHCP rather than PPPoE, and I believe it offers native IPv6, although their documentation for their implementation is much lacking. I used the Native setting for IPv6, which does provide the router with an IPv6 address as mentioned earlier.

I configured the VLAN using the GUI.
Screenshots attached for my config.

Have you tried PPPOE? I recall several people recieving their connections over VLAN (similar to the way your ISP does it) requiring to have to use PPPOE for their IPV6 connection type.

 

[drinkingbird]

Have you tried PPPOE? I recall several people recieving their connections over VLAN (similar to the way your ISP does it) requiring to have to use PPPOE for their IPV6 connection type.

Hopefully most ISPs have gone away from the tunnel model for IPv6 (the few that did it initially). You would think if he's getting a WANv6 IP and can traceroute from the router to google that it is working without PPPoE, but who knows. The breakdown seems to be somewhere between the WAN IP they're getting assigned and the LAN subnet being used from within that. The asus does seem to be routing traffic to the ISP's first hop from the LAN, just nothing beyond that.

 

[drinkingbird]

Wondering if anyone has been able to get IPv6 working using a WAN connection that utilises VLAN? In my country, VLAN tagging with ID 10 is required on the WAN port, with the IP address set using DHCP? I have had a trawl through the forums here but was unable to find any configs that people had working!

Another interesting symptom is when tracing from the router your ISP's next hop is responding much quicker than when tracing from your LAN (even though your LAN is only a few msec delay). I guess the IPv6 firewall in the router could be de-prioritizing ICMPv6 or just handling IPv6 more slowly. Just seems like a pretty high delay, which may mean even that first ISP hop is having some trouble with your LAN subnet.

 

[SomeWhereOverTheRainBow]

Hopefully most ISPs have gone away from the tunnel model for IPv6 (the few that did it initially). You would think if he's getting a WANv6 IP and can traceroute from the router to google that it is working without PPPoE, but who knows. The breakdown seems to be somewhere between the WAN IP they're getting assigned and the LAN subnet being used from within that. The asus does seem to be routing traffic to the ISP's first hop from the LAN, just nothing beyond that.

I believe he is getting PPPOE over VLAN via ISP as indicated by this :

Wondering if anyone has been able to get IPv6 working using a WAN connection that utilises VLAN? In my country, VLAN tagging with ID 10 is required on the WAN port, with the IP address set using DHCP? I have had a trawl through the forums here but was unable to find any configs that people had working!

I may be completely wrong, but he should at least try through trial and error before eliminating the thought.

 

[drinkingbird]

I believe he is getting PPPOE over VLAN via ISP as indicated by this :

Without configuring PPPoE on the router? I know he's got VLAN 10 on the WAN Port (configured via the GUI in the screenshot) but he is using DHCP and it is working fine for V4 and also is getting a v6 IP and can traceroute to a v6 destination from the router....

Having a VLAN tag on the WAN doesn't necessitate PPPoE - two totally different things.

 

[SomeWhereOverTheRainBow]

Without configuring PPPoE on the router? I know he's got VLAN 10 on the WAN Port (configured via the GUI in the screenshot) but he is using DHCP and it is working fine for V4 and also is getting a v6 IP and can traceroute to a v6 destination from the router....

Having a VLAN tag on the WAN doesn't necessitate PPPoE - two totally different things.

It is quite possible they offer dhcp and PPPOE option for the ipv4 aspect.

 

[drinkingbird]

It is quite possible they offer dhcp and PPPOE option for the ipv4 aspect.

From the screenshots and comments their WAN is configured for Automatic IP not PPPoE and IPv4 is working fine and IPv6 is mostly working. Maybe I'm missing something.

 

[SomeWhereOverTheRainBow]

From the screenshots and comments their WAN is configured for Automatic IP not PPPoE and IPv4 is working fine and IPv6 is mostly working. Maybe I'm missing something.

Or I am just wrong, Sorry.

 

[drinkingbird]

Or I am just wrong, Sorry.

Or we both are, or neither one of us are. Why can't everyone just shut off IPv6

 

[SomeWhereOverTheRainBow]

Or we both are, or neither one of us are. Why can't everyone just shut off IPv6

Well we need our advocate @Tech9 to explain how to "properly" do that. We don't want to tell him to just switch to "passthrough".

 

[drinkingbird]

Well we need our advocate @Tech9 to explain how to "properly" do that. We don't want to tell him to just switch to "passthrough".

Yeah I just added bold emphasis to my reply to make that more clear. If there is an ISP router in the path (really the only time passthrough should be needed, but we know that isn't always the case) and you trust its firewall, then it may be ok. If not, tread carefully.

 

[Tech9]

Well we need our advocate @Tech9 to explain how to "properly" do that.

I have no ISP with VLAN requirements and don't know what the problem is. As usual people want to try IPv6, create an issue and then fight it for reasons I don't understand. I'm waiting for new AX86U firmware because IPv6 Native breaks thing in 22068 that used to work before. Testing become more and more time consuming and the list of things to check grows longer (more issues introduced) instead of shorter (problems solved). This is very disappointing and I don't even have the will to run the test firmware at the moment. @rlh - seriously, don't enable anything you don't need.

 

[drinkingbird]

I have no ISP with VLAN requirements and don't know what the problem is. As usual people want to try IPv6, create an issue and then fight it for reasons I don't understand. I'm waiting for new AX86U firmware because IPv6 Native breaks thing in 22068 that used to work before. Testing become more and more time consuming and the list of things to check grows longer (more issues introduced) instead of shorter (problems solved). This is very disappointing and I don't even have the will to run the test firmware at the moment. @rlh - seriously, don't enable anything you don't need.

I'm waiting for IPv8. There is only one IP address for the entire world but 100 trillion ports.

 

[L&LD]

Still not enough for that future IPv8 world.

 

[SomeWhereOverTheRainBow]

I'm waiting for IPv8. There is only one IP address for the entire world but 100 trillion ports.

I imagine when that happens, it will be like Mario bros. Our data will just be popping in and out of pipelines all day. Mono-tone Mario music will be playing in the background.