 | reply to DrDrew
Re: [OK] Another day, another Cox outage Not with the Cisco I can't.
In the Moto, I would have a T3 rarely (1x/week?) but that's it, nothing else.
No, it was including the router. |
|
|
|
 DrDrewSo that others may surf. join:2009-01-28 SoCal kudos:8 1 edit | There aren't any default home router gateway IPs in the PingPlotter post, which is rather strange...
Are the LAN IPs in the default 192.168.x.x range or is it something different like 10.0.1.x range?
If your home router is using the 10.0.1.x range it may cause some odd issues since Cox probably uses that address space for modem management IPs. Most home routers I've seen don't block private IP address space traffic across the WAN port by default.
If you are using normal default 192.168.x.x home router LAN addressing, it's odd it doesn't show in the PingPlotter graph. -- Two is one, one is none. If it's important, back it up... Somethimes 99.999% availability isn't even good enough. |
|
 | I'm using a 192 range. It has never shown up on any pingplotter or tracert. |
|
 CoxTech1VIP join:2002-04-25 Chesapeake, VA kudos:72 | That's a little strange in itself. If you're running ping plotter from your PC the default gateway which would be your router should show up just like any other hop along the path. |
|
 | I agree that it's a little odd, but it seems that most Dlink routers do this for some reason. I've never bothered to figure out why.
FWIW, I never heard back yesterday, so I don't know the status of anything. However, yesterday afternoon, I did see 2 line trucks running up and down the street. |
|