Important note about SSL VPN compatibility for 20.0 MR1 with EoL SFOS versions and UTM9 OS. Learn more in the release notes.

Thread Info
  • State Suggested Answer
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 42 subscribers
  • Views 14027 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

Time Warner Cable Native IPV6

DavisDarvish1

Will the XG firewall work and provide native ipv6 access to the TWC network? I am a little out of date on my info as last i was runnin sophos was near the start of this year on utm 9 and it worked great on comcast with native ipv6.. not sure if this new version is different or if twc implementation of ipv6 is different



This thread was automatically locked due to age.
  • 0
    my utm 9.x works perfectly with TWC ipv6, they give me a whole /64 subnet to play with. not so the XG.
  • 0
    XG does not support native IPv6, very frustrating. XG also does not support sixxs tunnels.
    I have both networks at home, so very disappointed.

    Ian,

    home UTM 9.x running in ESXi 6 e3-1275v2

    AP55c and AP10 (courtesy Astaro)

    Three other UTMs, SUM and SFM in hibernation

    XG 15.x MR3 in hibernation

  • 0

    XG dies not support IPv6 DHCP-PD. So, it is impossible to get IPv6 addressing from your service provider (anybody on TWC, Comcast, Cox, etc. will have the same issue).

    This has been acknowledged by Sophos. But, no roadmap as to when it will be implemented. Definitely a show-stopper for me.

  • 0
    Okay, so another question.. is there a way to allow the XG to handle ipv4 and be the gateway and then run either an instance of UTM 9 or just use a windows server box to manage and route ipv6 traffic?
  • 0 in reply to DavisDarvish1
    As long as XG is the gateway router connected to your cable modem, there is no way to get TWC IPv6 addressing for your LAN and run true Native Dual Stack. But, there are still options.

    1) IPv6 ULA and Masquerading (Not certain XG will support this .. you need to try) - Use IPv6 ULA addressing on the LAN. If XG is getting an IPv6 address on the WAN, then configure IPv6 masquerading (think NAT). I'm doing this for a couple of networks on UTM since it lacks the functionality to request more that a single /64.

    2) Tunneling the IPv6 traffic (6-in-4) to a provider like Hurricane Electric (https://tunnelbroker.net). The configuration options are there in XG to do this directly on the platform. Haven't seen anybody confirm that it actually works.

    3) Tunneling the IPv6 traffic (6-in-4) from another device residing on the LAN - The device would be the tunnel end point and advertise the RA as being the IPv6 default router. Be sure XG is able to forward IP Protocol 41.

    For me, I decided to stick with UTM, which is a much better platform and not go back in time.
Unfiltered HTML