Hi Bill,
Sorry for the lack of detail, but I'm sure you can appreciate the
difficulty in posting output when you have no internet connection.
I doubt this is an ISP problem, becuase the two other computers in the
house (both laptops) connect just fine. One laptop has Windows and one
is another Debian box (running Sarge), so that is why it is something
internal to this particular machine.
Here is some output from the problem system:
ansum:~# date
Tue Sep 28 19:27:34 EDT 2004
ansum:~# uptime
19:27:40 up 5 min, 3 users, load average 0.76, 0.59, 0.26
ansum:~# /sbin/pump -i eth0 --status
Device eth0
IP: 66.203.194.71
Netmask: 255.255.255.0
Broadcast: 66.203.194.255
Network: 66.203.194.0
Boot server: 66.203.195.237
Next server: 192.168.15.83
Gateway: 66.203.194.1
Gateways: 66.203.194.1
Boot file: vxWorks
Domain: cp.telus.net
Nameservers: 66.203.195.237
Ntpservers: 192.168.15.83
Renewal time: Tue Sep 28 22:03:24 2004
Expiration time: Tue Sep 28 22:25:54 2004
ansum:~# ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:05:5D:FD

E:9E
inet addr:66.203.194.71 Bcast:66.203.194.255
Mast:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
..
..
..
ansum:~# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref
Use Iface
66.203.194.0 0.0.0.0 255.255.255.0 U 0 0
0 eth0
0.0.0.0 66.203.194.1 0.0.0.0 UG 0 0
0 eth0
ansum:~# ping
www.google.com
ansum:~# ping 66.203.195.237
PING 66.203.195.237 (66.203.195.237): 56 data bytes
--- 66.203.195.237 ping statistics ---
4 packets transmitted, 0 packets received, 100% packet loss
ansum:~# ls -l /etc/resolv.conf
-rw-r--r-- 1 root root 46 Sep 28 19:25 /etc/resolv.conf
So, it seems the interface is set up correctly, but I can't get
anywhere. This is not a resolv.conf issue, because it works just fine
with the other computers.
Any suggestions?
David
(E-Mail Removed) (Bill Unruh) wrote in message news:<cj486t$29e$(E-Mail Removed)>...
> (E-Mail Removed) (David Ballantyne) writes:
>
> ]Hi,
>
> ]I've encountered a very strange problem, which I need a Linux guru to
> ]help me out with. I'm running Debian Sarge with Linux 2.4.26.
>
> ]I've been connecting to the internet using /sbin/pump -i eth0, and
> ]that had been working fine. I was away for three weeks and had my
> ]computer off, and then, when I got back, and turned it back on I found
> ]I can no longer connect. The wierd thing is that pump can still
> ]negotiate a connect with the DHCP server, e.g., if I do a /sbin/pump
> ]-i eth0 --status it lists all the right details, which are the same as
> ]the ones listed by 'ifconfig'. But, I can't ping or connect to
> ]anything outside my machine -- not the DNS server, not www.google.com,
> ]nothing. But, my computer knows all the right addresses, etc. Its very
> ]perplexing. I emphasize that absolutely nothing has changed from when
> ]it was working three weeks before and now. I'm wondering if I have
> ]something compiled in the kernel which may be confusing the machine at
> ]times, but I'm not familiar enough with the details to know where to
> ]look.
>
> ISPs can easily change things in three weeks.
>
> a) What is the output of route -n
> b) do you get an IP address (ifconfig -a). Is it similar to what you had
> befor? If it is different, is your firewall set up to reject everything but
> your old address?
> c) "It lists all the right details" -- you admit you are stumped. Are you
> sure you know what the "right details" are? Or perhaps if you published the
> details here might someone else see something you had missed?
> d) "My computer knows all the right addresses" means what?