Contributor
•
22 Messages
Unable to ping WAN IPv4 Gateway since last planned maintenance (15-December-2022)
Just to first say I don't have any issues connecting to the internet, this is more of an observance that the IPv4 gateway IP doesn't respond to ICMP and actually a question of whether this is a known change of behavior.
As the subject mentions since the last planned maintenance last week it would seem the IPv4 Gateway assigned from xfinity doesn't respond to ping (ICMP). My router has a feature that will monitor the IPv4 Gateway IP using ping to determine if the WAN interface is up or down. The monitor has showed 100% packet loss since the maintenance.
For example after the big outage in mid November I was assigned a new IP which DHCP also set the IPv4 gateway to 66.41.216.1 - router logs show no issues up until the maintenance on late 15-December / early 16-December. The route shows the IPv4 Gateway IP assigned was 66.41.232.1 but with the same IPv4 address I already had. The router attempts to ping 66.41.232.1 all fail (100% packet loss).
I'm able to workaround the router showing the WAN GW is down by using another IPv4 address such as a DNS server but wanted to ask if this expected with recent changes or does this perhaps identify some other upstream problem. Again, none of our devices have any connection issues, it's just a warning that I have found a workaround for. Interesting enough the IPv6 Gateway IP that is assigned works just fine with the monitoring the router is doing.
TIA
lnxfrk
Contributor
•
22 Messages
2 years ago
It seems a lot like this thread https://forums.xfinity.com/conversations/your-home-network/cannot-ping-comcast-gateway-ip-after-maintenance-outage/6324da992ff2c66589ffe60f
5
0