Re: intermittent cable connection
From: Troy Piggins (usenet_at_piggo.com)
Date: 12/09/04
- Next message: jpd: "Re: Please excuse. Don't bother, just having a problem with comp.*"
- Previous message: Troy Piggins: "Re: intermittent cable connection"
- In reply to: Doug Freyburger: "Re: intermittent cable connection"
- Next in thread: Doug Freyburger: "Re: intermittent cable connection"
- Reply: Doug Freyburger: "Re: intermittent cable connection"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Thu, 09 Dec 2004 05:45:18 GMT
* Doug Freyburger wrote:
> Save the routing table at both times and compare them. Likely
> they will be different. If so consider switching to a static default
> route
> on it to point out the *interface* to the ISP. That way when the ISP's
> DHCP lease expires and your IP number changes, it will continue
> working.
> Do theLinux routing commands allow setting the default route to an
> interface rather than to the IP of a gateway? Some versions do some
> don't.
Working :
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
192.168.0.0 * 255.255.255.0 U 0 0 0
eth1
147.10.92.0 * 255.255.252.0 U 0 0 0
eth0
169.254.0.0 * 255.255.0.0 U 0 0 0
eth1
127.0.0.0 * 255.0.0.0 U 0 0 0
lo
default CPE-147-10-92-1 0.0.0.0 UG 0 0 0
eth0
Not working :
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
192.168.0.0 * 255.255.255.0 U 0 0 0
eth1
147.10.92.0 * 255.255.252.0 U 0 0 0
eth0
169.254.0.0 * 255.255.0.0 U 0 0 0
eth1
127.0.0.0 * 255.0.0.0 U 0 0 0
lo
default 147.10.92.1 0.0.0.0 UG 0 0 0
eth0
Both look the same, except working is hostname for default, while not is
just IP.
> Save your ifconfig -a output and anything about DHCP configs while
> working and while not. If your lease is expiring hourly you'll be able
> to figure it out that way and react accordingly.
Nothing different between working and not.
> Next check DNS cache timeouts. If it works for an hour then doesn't
> work for an hour then does again, it sounds very much like a round
> robin where one of the IP numbers in the cycle works and one
> doesn't. Use dig or nslookup to find the SOA record of your ISP to
> find the TLL entry it uses and very likely it will be 3600, an hour.
> Then look closely at the IP numbers offered by your ISP. If you're
> going to a name, you may want to switch to it's hard-coded IP
> number if this is happening.
? How to check DNS cache timeout? What is this going to achieve? I
don't seem to have actual login problems, provided I can get the network
connection. I am going ot check a new network card tonight and see if
that is it.
All services seem to be running fine. The reason I hadn't thought of
network card fault is that even when network down, I can ping it. Can't
ping the modem though. But ISP replaced the modem yesterday but the
problem remains, so will try hardware.
Will keep you posted.
-- T R O Y P I G G I N S e : usenet@piggo.com
- Next message: jpd: "Re: Please excuse. Don't bother, just having a problem with comp.*"
- Previous message: Troy Piggins: "Re: intermittent cable connection"
- In reply to: Doug Freyburger: "Re: intermittent cable connection"
- Next in thread: Doug Freyburger: "Re: intermittent cable connection"
- Reply: Doug Freyburger: "Re: intermittent cable connection"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
