Business Community > Gateways > IPv6 Cannot Reach WAN - ER8411
< Gateways

IPv6 Cannot Reach WAN - ER8411

IPv6 Cannot Reach WAN - ER8411

IPv6 Cannot Reach WAN - ER8411
IPv6 Cannot Reach WAN - ER8411
2025-05-23 18:01:58 - last edited Sunday
Tags: #WAN Setup #IPv6
Model: ER8411  
Hardware Version: V1
Firmware Version: 1.3

Been trying to get IPv6 working for a few days on the ER8411, but it seems to have an issue routing anything to the WAN interface.

 

To preface this, I know IPv6 is working from my ISP side as I can get it to work on another device and reach the any address on WAN (for example google DNS 2001:4860:4860:8888).

 

When the ER8411 is configured to use DHCPv6, I can successfully get the following from my ISP:

- get a non-temporary address

- DNS server addresses

- 60 bit prefix

 

On the LAN side, I configured SLAAC+Stateless DHCP to use the delegated prefix, but nothing on my LAN can reach anything on WAN.  Attempting to ping the router non-temporary address, or delegated addresses fails even when enabling ACL to allow all inbound IPv6 traffic and Ping from WAN.

 

This is where I started to dig a little deeper.  I noticed that the ER8411 was listing nothing for the gateway address, despite as mentioning above everything else seemed to imply it coordinated properly with my ISP.

 

Remembering my ISP uses DHCPv6, and does not send any RA's (confirmed this with another device via Wireshark), my best guess is the ER8411 doesn't automatically assume a gateway, and always expects it be found via RA.  This makes sense as the device I used to originally confirm everything was fine from the ISP side (at least given correct routing info) required me to manually specify the gateway as the link local address for my ONT.

 

Is there a way around the lack of RA's while still using DHCPv6 on the ER8411?  Or am I interpreting this data wrong and am on the complete wrong track to solving this?

 

Edit: The ONT appears to be indicating it is a router in it's neighbor advertisement, so this is probably how my ISP's hardware works.

 

  0      
 
  0      
 
#1
Options
1 Accepted Solution
Re:IPv6 Cannot Reach WAN - ER8411 -Solution
a week ago - last edited Sunday

  @mbze430 

mbze430 wrote

  @Clive_A 

I still can't get the ER8411 to enable IPV6.  Every time I try enable on the WAN side, it takes about 10-15mins to reboot (I think that's what it is doing) when it comes back it still have no IPV6 and the check mark is gone. 

 

Same as OP I know I can get DHCPv6 from Spectrum before moving to the Omada environment (pfsense).

 

Is there a specific "order" to get IPV6 going?  at least get something from my ISP?

WAN IN ACL is required if you want to expose IPv6 and reach the router from a remote IPv6. 

Recommended Solution
  1  
  1  
#5
Options
6 Reply
Re:IPv6 Cannot Reach WAN - ER8411
2025-05-26 07:57:33

  @thePrince 

You are trying to log in to the page of the ER8411 via v6?

Resolving the DNS does not mean you can access the router page.

You make sure both sides are configured with IPv6 and capable of IPv6.

 

At least on the ER8411, WAN IPv6 should be the IP you use for access. Try to ping it while you disable the Block Ping from WAN. And also make sure you have ACL enabled for ICMP incoming.

Regarding your IPv6 setup, you might take a look at guides on the Internet about IPv6 access. It would be best to use bridge mode on ISP devices.

  0  
  0  
#2
Options
Re:IPv6 Cannot Reach WAN - ER8411
2025-05-26 15:23:32

  @Clive_A 

 

Haven't tried to access the web UI since it's adopted.

 

Was simply pinging some address like Google's DNS or ping my router's GUA from outside (with ping from WAN allowed and IPv6 ACL to allow), neither work.

 

Yes, both sides are capable of IPv6, I confirmed with another device I can get everything working.  As noted I think the issue here is my ISP doesn't use Router Advertisements, so the Er8411 can't find a default gateway for the WAN connection, and there is no way to override it when DHCPv6 is selected.

  0  
  0  
#3
Options
Re:IPv6 Cannot Reach WAN - ER8411
a week ago

  @Clive_A 

I still can't get the ER8411 to enable IPV6.  Every time I try enable on the WAN side, it takes about 10-15mins to reboot (I think that's what it is doing) when it comes back it still have no IPV6 and the check mark is gone. 

 

Same as OP I know I can get DHCPv6 from Spectrum before moving to the Omada environment (pfsense).

 

Is there a specific "order" to get IPV6 going?  at least get something from my ISP?

  0  
  0  
#4
Options
Re:IPv6 Cannot Reach WAN - ER8411 -Solution
a week ago - last edited Sunday

  @mbze430 

mbze430 wrote

  @Clive_A 

I still can't get the ER8411 to enable IPV6.  Every time I try enable on the WAN side, it takes about 10-15mins to reboot (I think that's what it is doing) when it comes back it still have no IPV6 and the check mark is gone. 

 

Same as OP I know I can get DHCPv6 from Spectrum before moving to the Omada environment (pfsense).

 

Is there a specific "order" to get IPV6 going?  at least get something from my ISP?

WAN IN ACL is required if you want to expose IPv6 and reach the router from a remote IPv6. 

Recommended Solution
  1  
  1  
#5
Options
Re:IPv6 Cannot Reach WAN - ER8411
a week ago - last edited a week ago

  @Clive_A Could you explain more about what this rule should look like?

 

I just had Telus Fiber setup. I have bypassed their NAH by pluggin the SFP into my ER7206. I am able to get an IPV4 address but not an IPV6 address. 

 

When I use "Get IPv6 Address" set to "Automatically" and click Connect on the Device Details It fails to get anything. When I set it to "Via DHCPv6" I seem to get a Link Local Address, DNS servers are set, but I dont get an IP Address

 

 

  0  
  0  
#6
Options
Re:IPv6 Cannot Reach WAN - ER8411
Sunday

  @ProtoTempus 

ProtoTempus wrote

  @Clive_A Could you explain more about what this rule should look like?

 

I just had Telus Fiber setup. I have bypassed their NAH by pluggin the SFP into my ER7206. I am able to get an IPV4 address but not an IPV6 address. 

 

When I use "Get IPv6 Address" set to "Automatically" and click Connect on the Device Details It fails to get anything. When I set it to "Via DHCPv6" I seem to get a Link Local Address, DNS servers are set, but I dont get an IP Address

 

 

 

If you describe that you don't even get an IP from the ISP, that seems to be a WANv6 config problem instead of a problem similar to the OP.

You gotta fix this first. The picture looks good but you still need to make sure that ISP provided device has set it to Bridge mode. Or you should try with the Non-address instead. 


WAN IN ACL is GW ACL which you allow WAN-LAN direction and IPv6 should be allowed. 

 

  1  
  1  
#7
Options

Information

Helpful: 0

Views: 403

Replies: 6

Tags

WAN Setup IPv6
About Us
Press
Copyright © TP-Link Systems Inc. All rights reserved.