Lost IPv4 Gateway with Vigor 130 and pfsense

[mmarooth]

So I have Sky Broadband and Starlink.  I have Sky coming in through a Vigor 130 modem with both Sky and SL going into pfsense 2.7.0.  All has been fine for a couple of years running in failover mode. (Wife & I both work from home & need connectivity).  A bunch of HA devices and a couple of Unifi AP's are spread through the house as well as connected television, SONOS speakers, Sky Q etc.  My rack of servers for my work is also connected however all the VM's and storage are on a seperate network.  Nothing on the network side has been changed and I have no other DHCP servers in the network.

I can see in pfsense that on the Sky IPv4 Gateway it is offline with 100% packet loss however the IPv6 Gateway is perfectly fine.  Both gateways on the Starlink side are fine so I'm currently switched over to Starlink.

I ran a service test through the Sky website which reported that everything was OK with no faults.  I cannot for the life of me get to the bottom of what might be going on with Sky.  Is it possible that I am being affected by MAP-T? 

I'm in a rural location so have copper to the house.  How do I find out whether MAP-T is enabled on my line and opt-out so I can see if that resolves my issue?

Grateful for any suggestions or pointers.  

[TimmyBGood]

@mmarooth 

Just a guess, but might this apply?

https://helpforum.sky.com/t5/Broadband/Sky-Fibre-amp-Unifi-Dream-Machine/m-p/4735717/highlight/true#... 

[mmarooth]

@TimmyBGood I don't have a Dream machine, I manage the AP's using a VM Appliance however I am grateful for the pointer.  I did try to disable the IPv6 Gateway for Sky in pfsense but that made no difference unfortunately.

I'm going to upgrade pfsense to 2.7.2 once my dear wife finishes her final conference call of the day but I'm fairly sure this is not a pfsense issue.  I'm encouraging her to finish early with some sweet treat baking 🙂

I'm still wondering whether Sky think that my Vigor 130 will support MAP-T when it does not.  

Mark

[mmarooth]

Ok so I think I might be the donut here!!!!

pfsense monitors the gatewaysby pinging something.  My pfsense has been set up to ping the Sky IPv4 DHCP server which has been working well for the best part of two years.

Continuing my diagnostics I switched my Vigor 130 from one network port to another on my pfsense box and reconfigured the ports in pfsense just in case it was a banjaxed network port.  I got a new WAN address which I would expect.  Ran a "What's my IP" and got the right result so then I tried to ping the Sky DHCP server from a terminal and got no response.

Changed the monitor IP address for the Gateway to a well known DNS server and blow me but pfsense is telling me that the interface is fine with zero packet loss.

My conclusion, I used to be able to ping the Sky IPv4 DHCP server but can no longer hence pfsense went doolally telling me the Gateway was down and I just assumed it was.  If that is the case then I'm a happy camper but perhaps should have checked that first instead of jumping to conclusions.

You know what they say about assume.... It makes an **bleep** out of U and Me. In this case me 🙂

I'm a software and embedded hardware engineer, not a network engineer.  At least I learned something.

Will keep an eye on it over the next wee while but hopefully I can reinstate my load-sharing/failover and all will be good.