Subject: Router/Cable modem woes
From: Noozer
Date: 11/11/2007 4:36:21 PM
"General Schvantzkopf" <schvantzkopf@yahoo.com> wrote in message
news:y8idncKy2JBDmaranZ2dnUVZ_s7inZ2d@comcast.com...
> This is not a Linux question except peripherally. I have a Dlink DIR 655
> Wireless N + gigabit router, connected to a Comcast cable modem. The
> performance is excellent when it works but in the last few days it's been
> getting into a state where it stops working, power cycling the router
> restores my web access. I'm not sure if this is the routers fault or the
> Cable modems problem.
I have heard that the 655 has problems with maintaining a connection on some
ISPs using Cisco uBR routers.
I know that I could not connect after updating to the latest firmware on
DLinks website. I backed down to v1.03 and our connection seems to have
stabilized.
Definately something you should ask your ISP and DLink about, as they may
want to have you run some test to collect any related info that they can
get.
Subject: Router/Cable modem woes
From: Noozer
Date: 11/11/2007 9:58:29 PM
> When things go bad I can still access all of my machines on the LAN and I
> can access the Router. The problem is that I can't access the Internet. I
> also can't access my machines from the Internet. I first noticed this
> problem when I was at a customer site and I tried to ssh into my CVS
> server. I wasn't able to ssh into either of my ssh ports, several hours
> later I was able to get in. The next morning I wasn't able to get out
> from any of my machines. Power cycling the modem didn't help but power
> cycling the router did.
Exactly the problem that I've been told about.
In an attempt to maintain connectivity from the outside, I've got one of my
machines that pings my DNS server one time every minute. Haven't really had
the chance to see if it's improved connectivity from the outside.
I haven't had any issue maintaining a connection from the inside to the
internet though. The only two things that I can think of that I altered was
to allow ping replies from the WAN and hardcoded the WAN port to 100mb
instead of auto detection.
|