Hi all

Over the last two weeks I've been seeing issues with certain remote users coming in to my WatchGuard Firebox using their SSL VPN (which is OpenVPN with a skin and a config control channel) on my 2degrees (ex-Snap network still) fibre connection. Users either don't get a config down from the Firebox, they fail to connect after getting one, or they connect but have issues with RDP once connected.

Switching them out to OpenVPN with the .ovpn file from the Firebox doesn't resolve it, unless I remove the 2degrees connection entirely and let it come in on my Voyager one which is configured as a backup for inbound VPN.

So far it has affected about half a dozen Starlink users and two on managed fibre, neither of which knows who manages it.

When it was just Starlink I assumed it was a routing issue and worked around it. The other two being fibre concerns me a bit.

Are there any reports around about routing issues to 2degrees, or changes on their network? I would call them, but the last time I tried logging a fault with business support I had a call back from one of their mobile resellers in Auckland about my plan - and when pressed said that what they were planning would change my static IP and drop the /29 network so I'm a little nervous about calling them about this.

So tl;dr - 2degrees is scrambling inbound WatchGuard VPN/OpenVPN on 443. Working fine on Voyager on the same box.