Re: EdgeRouter Periodically Loses Connection

I've been running a continuous ping this afternoon to three addresses.

• 192.168.1.254 is the inside LAN1 interface. \
• 192.168.100.1 is the cable modem.
• 8.8.8.8 is Google DNS.

All three of these were running simultanously and I'm including the output from the last few pings from each.

Again, these were all running at the same time. If I was able to ping through the router to the cable modem, but not beyond that to Google's Public DNS, any thoughts? ISP responsible? Or still something I could set on my router to resolve?

Internal LAN1 interface:

Reply from 192.168.1.254: bytes=32 time<1ms TTL=64
Reply from 192.168.1.254: bytes=32 time<1ms TTL=64
Reply from 192.168.1.254: bytes=32 time<1ms TTL=64
Reply from 192.168.1.254: bytes=32 time<1ms TTL=64
Reply from 192.168.1.254: bytes=32 time<1ms TTL=64
Reply from 192.168.1.254: bytes=32 time<1ms TTL=64
Reply from 192.168.1.254: bytes=32 time<1ms TTL=64
Reply from 192.168.1.254: bytes=32 time<1ms TTL=64
Reply from 192.168.1.254: bytes=32 time<1ms TTL=64
Reply from 192.168.1.254: bytes=32 time<1ms TTL=64
Reply from 192.168.1.254: bytes=32 time<1ms TTL=64
Reply from 192.168.1.254: bytes=32 time<1ms TTL=64
Reply from 192.168.1.254: bytes=32 time<1ms TTL=64
Reply from 192.168.1.254: bytes=32 time<1ms TTL=64
Reply from 192.168.1.254: bytes=32 time<1ms TTL=64
Reply from 192.168.1.254: bytes=32 time<1ms TTL=64
Reply from 192.168.1.254: bytes=32 time<1ms TTL=64

Ping statistics for 192.168.1.254:
    Packets: Sent = 7588, Received = 7588, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 7ms, Average = 0ms

Cable Modem:

Reply from 192.168.100.1: bytes=32 time<1ms TTL=63
Reply from 192.168.100.1: bytes=32 time<1ms TTL=63
Reply from 192.168.100.1: bytes=32 time<1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time<1ms TTL=63
Reply from 192.168.100.1: bytes=32 time<1ms TTL=63
Reply from 192.168.100.1: bytes=32 time<1ms TTL=63
Reply from 192.168.100.1: bytes=32 time<1ms TTL=63
Reply from 192.168.100.1: bytes=32 time<1ms TTL=63
Reply from 192.168.100.1: bytes=32 time<1ms TTL=63
Reply from 192.168.100.1: bytes=32 time<1ms TTL=63
Reply from 192.168.100.1: bytes=32 time<1ms TTL=63
Reply from 192.168.100.1: bytes=32 time<1ms TTL=63
Reply from 192.168.100.1: bytes=32 time<1ms TTL=63
Reply from 192.168.100.1: bytes=32 time<1ms TTL=63
Reply from 192.168.100.1: bytes=32 time<1ms TTL=63

Ping statistics for 192.168.100.1:
    Packets: Sent = 7567, Received = 7567, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 19ms, Average = 0ms

Google Public DNS:

Reply from 8.8.8.8: bytes=1 time=26ms TTL=47
Reply from 8.8.8.8: bytes=1 time=24ms TTL=47
Reply from 8.8.8.8: bytes=1 time=25ms TTL=47
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 8.8.8.8: bytes=1 time=25ms TTL=47
Reply from 8.8.8.8: bytes=1 time=27ms TTL=47
Reply from 8.8.8.8: bytes=1 time=24ms TTL=47
Reply from 8.8.8.8: bytes=1 time=27ms TTL=47
Reply from 8.8.8.8: bytes=1 time=25ms TTL=47
Reply from 8.8.8.8: bytes=1 time=25ms TTL=47
Reply from 8.8.8.8: bytes=1 time=24ms TTL=47

Ping statistics for 8.8.8.8:
    Packets: Sent = 7599, Received = 7592, Lost = 7 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 22ms, Maximum = 51ms, Average = 25ms