Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 23 replies
  • Subscribers 30 subscribers
  • Views 31712 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

WAN IPV6 in XG v17. Is there a trick to it?

Casual_User

Hello, 

I've been running XG firewall with IPV4 LAN and WAN for the past year.  I am currently running XG 17 MR3.  I decided to experiment with IPV6.  Under Interfaces I set the WAN port to use IPV6 DHCP Auto.  It appeared to connect via IPV6 since it found the IPV6 Gateway and it gave me a "green light" in the WAN Link Manager.  But I had no internet access through the firewall.  I tried pinging IPV6 sites and accessing IPV6 sites to no avail.  For comparison, I disconnected the XG firewall from the modem and connected my laptop directly to the modem.  My Windows 10 laptop quickly connected to the modem using IPV6 and found the same IPV6 gateway.  I was able to surf the internet with my laptop accessing IPV6 sites.  I had no special settings in Windows 10, just set it to automatically connect with DHCP.

So if the laptop could connect without issue, why can't the XG firewall connect?



This thread was automatically locked due to age.
Parents
  • 0

    Quick update,

    I've got IPV4/IPV6 dual stack working.  Once the binding issue was resolved with the ISP and having them turn on dual stack at their end, I got it up and running.  I managed to get the router advertisement working too.  The most difficult part at my end was getting the connection with the ISP.  My connection does not work if I have it on "Auto".  The only way it works is if I have it set to "DHCP" + "Manual" + "DHCP Only".

    Documentation is quite inadequate.  While there seems no end of information that explains the intricacies of IPV6 addressing and the history of the IP protocols, there is definitely a lack of simple information as to what IP to assign your internal LAN and the prefix that should be used by the router advertisement.

    I definitely have no immediate plans on using IPV6 for my LAN setup.  Too many bits to worry about when assigning IP addresses to the couple of servers that I have.  IPV4 is far easier for me to track mentally.

    My guest WiFi network cannot use IPV6 but the home WiFi that is bridged to LAN has no issues using IPV6.  I'm not sure why there would be a difference.  Perhaps an oversight on behalf of Sophos?

    Thanks.

Reply
  • 0

    Quick update,

    I've got IPV4/IPV6 dual stack working.  Once the binding issue was resolved with the ISP and having them turn on dual stack at their end, I got it up and running.  I managed to get the router advertisement working too.  The most difficult part at my end was getting the connection with the ISP.  My connection does not work if I have it on "Auto".  The only way it works is if I have it set to "DHCP" + "Manual" + "DHCP Only".

    Documentation is quite inadequate.  While there seems no end of information that explains the intricacies of IPV6 addressing and the history of the IP protocols, there is definitely a lack of simple information as to what IP to assign your internal LAN and the prefix that should be used by the router advertisement.

    I definitely have no immediate plans on using IPV6 for my LAN setup.  Too many bits to worry about when assigning IP addresses to the couple of servers that I have.  IPV4 is far easier for me to track mentally.

    My guest WiFi network cannot use IPV6 but the home WiFi that is bridged to LAN has no issues using IPV6.  I'm not sure why there would be a difference.  Perhaps an oversight on behalf of Sophos?

    Thanks.

Children
No Data