Thread Info
  • State Suggested Answer
  • +2 person also asked this people also asked this
  • Locked Locked
  • Replies 34 replies
  • Answers 3 answers
  • Subscribers 13 subscribers
  • Views 91563 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

IPv6 in broken state

Ben

IPv6 has been unuseable latetly. Its not just about the unsupported PD-IA over PPPoE which has not been fixed since i reported it 1 1/2 years ago (several times and in beta), but with the last few updates IPv6 seems to only work in midnight during full moon if you spell the right chants. Sometimes it works, sometimes i need to restart the UTM a few times turn off/on IPv6.

Is anyone else having these problems?

If Sophos is reading this: when are you going to fix remaining buggy implementation?



This thread was automatically locked due to age.
  • 0

    Hey JoshSauer,

    thank you for your advice. I edited "/var/chroot-dhcpc/etc/default.conf" like it´s written here: 

    https://community.sophos.com/products/unified-threat-management/f/52/t/79288

    removed the entry "interface-mtu" and restarted the interface. 

    unfortunately without success.

    it was not previously possible to adapt for you the MTU value as grayed or similar?

  • 0 in reply to ThorstenMimel

    it was editable, but each time I changed it, the dhcp server's value would be put back in place within moments. It's a bug that Sophos knows about, but hasn't resolved yet.

    This was the only change I made and I'm now able to get my IPv6 address. I had to reboot my device (virtual machine) for the change to take effect. Just stopping and starting the interface did not work.

  • 0 in reply to JoshSauer

    can we get some official update please on this official community forum about the broken IPv6 implementation and ETA on fix please? :) 

    ---

    Sophos UTM 9.3 Certified Engineer

  • 0

    The problem existing when I was running on bare metal and after I moved to ESXi.

    This has been going on for months so it's clearly not much of a priority.

    I'm not writing to complain and I'm not asking you to fix it. What I'm writing to tell you here is that I regret the investments I've made in proprietary access points and RED's. I'm telling you I'm embarrassed I extolled the virtues of your platform to my IT director and V.P. I'm telling you this degeneration began when the name on the product changed.

     

  • 0

    so after Sophos UTM IPv6 kind-of working behind another router for about 2 weeks it finally stopped working again on my clients and internal network. Ping wouldn't get out, IPv6 Sites couldn't be opened.

    The Solution? I enabled outgoing masquarding from my internal network ipv6 to WAN, IPv6 worked again (through the WAN IPv6 of the sophos of course), so i disabled it again. IPv6 kept working and showing up my Internal LAN IPv6 again on whatismyip websites. 

    Maybe this helps anyone .. btw - reconnection, dis-/enabling ipv6 .. it all didn't help ... turning MASQ on/off .. that worked .. go figure

     

    FIX IPV6 or remove it completely from the UTM. Anything else is just a patch-together of non or kind-of-working solution. 

    ---

    Sophos UTM 9.3 Certified Engineer

  • 0 in reply to Ben

    I'm also trying IPv6 on the UTM. Unfortunately it doesn't work without outbound MASQ :( this is not the way IPv6 should work.

  • 0 in reply to Clemens von Bluecher

    Just to add a positive note, IPv6 worked on both VM and physical UTMs. IPv6 was used in both sixxs and native setup and has not failed. Currently I have a new install on a asus server motherboard.

    XG115W - v20.0.2 MR-2 - Home

    XG on VM 8 - v21 GA

    If a post solves your question please use the 'Verify Answer' button.

  • 0

    opened a Ticket through our Partner on Jan 5th 2017 (#6865033) - no reaction so far. Also bought another Sophos UTM that will serve IPv6 Endpoints eventually. Will see how it works out.

    ---

    Sophos UTM 9.3 Certified Engineer

  • 0 in reply to Ben

    Ticket through our Partner got closed by Sophos due to not having gold status or better.

    I opened up a new ticket on a licenced SG230 that ia also opened for support, ticket ID #7001011 and communicated this.

    let's see where this leads and if we can get a fix after over 2 years.

    ---

    Sophos UTM 9.3 Certified Engineer

  • 0 in reply to Ben

    our own (new) ticket also got closed due to the need of having a partner with gold/platinum status

     

    tldr: no gold/platinum partner, no support from sophos!

    ---

    Sophos UTM 9.3 Certified Engineer

Unfiltered HTML