reported this in 9.3 aswell,
when setting up WAN Connection over PPPoE the sophos is unable to get a prefix delegated to use for IPv6.
other routers i tested are able to get a /48 IPv6 Prefix with the same connection.
reported this in 9.3 aswell,
when setting up WAN Connection over PPPoE the sophos is unable to get a prefix delegated to use for IPv6.
other routers i tested are able to get a /48 IPv6 Prefix with the same connection.
---
Sophos UTM 9.3 Certified Engineer
Sophos, I'm disappointed. Again.
I'm so glad that Sophos is a professional security/networking company, and that they finally fixed this. Because in the opensource world or consumer grade products they couldn't get this to work for years.. Oh wait.........
i could live with this bug if sophos would comment on this and says its currently not possible or too time consuming to fix. But we are just getting ignored on this one.
---
Sophos UTM 9.3 Certified Engineer
So.. No news is good news?
Or is ignoring and hoping the users will go away the way to go?
i bet my 2 cents on that we will get ignored because it has no business case. I really wonder why even bother with a "community" like this if it ends beeing a user to user Forum without better Sophos Feedback. I will ask at the sophos booth at the cebit fair but i do not expect a real answer.
---
Sophos UTM 9.3 Certified Engineer
How is it that I'm not surprised?
Glad that you confirmed, I wasn't much like removing my good 'ol OpenWRT router, reconfiguring my WAN interface, patching cables...
Hi guys,
have you tried compring the logs from the devices you are getting an assigned /56 to that of the UTM to see if that shows any point of reference that you can identify as failing?
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