I can no longer see anything...!

Thymox · 11-19-2002, 01:44 PM

I think I figured out what was causing my problem here (something about an error in one of the primary libraries - that'll teach me to go updating to unstable stuff!) but now I've got a new one, and I'm certain that they're not related:

I couldn't be bothered to fart-arse about trying to sort out the library error considering the whole thing would fall over at seemingly random times, so I simply opted for a spring clean reinstall.

I can now, however, not access anything network related. I cannot ping anyone, not my gateway nor the machine that is sitting next to it (the one that I'm typing this on). The lights on the NIC itself are on and flashing, the lights on the switch are on and flashing, the correct modules are loaded, the correct settings have been applied (static IP, correct netmask, correct gateway IP, correct dns, the lot) and yet I cannot ping anything (except loop).

A normal ping from this box looks like:

Code:

PING 192.168.0.1 (192.168.0.1) from 192.168.0.15 : 56(84) bytes of data.
64 bytes from 192.168.0.1: icmp_seq=1 ttl=255 time=0.823 ms
64 bytes from 192.168.0.1: icmp_seq=2 ttl=255 time=0.800 ms
64 bytes from 192.168.0.1: icmp_seq=3 ttl=255 time=0.793 ms

--- 192.168.0.1 ping statistics ---
3 packets transmitted, 3 received, 0% loss, time 2014ms
rtt min/avg/max/mdev = 0.793/0.805/0.823/0.026 ms

however, a ping from the non-working box looks as such:

Code:

PING 192.168.0.1 (192.168.0.1) from 192.168.0.14 : 56(84) bytes of data.
From 192.168.0.14 icmp_seq=1 Destination Host Unreachable
From 192.168.0.14 icmp_seq=2 Destination Host Unreachable
From 192.168.0.14 icmp_seq=3 Destination Host Unreachable

--- 192.168.0.1 ping statistics ---
4 packets transmitted, 0 received, +3 errros, 100% loss, time 3027 ms
, pipe 3

Any thoughts?

Bert · 11-19-2002, 02:04 PM

Eh?

How and where does your NIC get it's IP address from? Don't you need to start /sbin/dhcpcd
?

Bert

vladkrack · 11-19-2002, 02:06 PM

Have you already look at your routes?

Thymox · 11-19-2002, 02:11 PM

No - we're running on statics here, it makes life much simpler! Here's my ifconfig (for eth0):

Code:

eth0      Link encap:Ethernet  HWaddr 00:D0:70:01:69:B2
          inet addr:192.168.0.14  Bcast:192.168.0.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:117 errors:0 dropped:0 overruns:0 frame:0
          TX packets:550 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          RX bytes:12913 (12.6 Kb)  TX bytes:39484 (38.5 Kb)
          Interrupt:10 Base address:0x30000

Thymox · 11-19-2002, 02:14 PM

Quote:

Originally posted by vladkrack
Have you already look at your routes?

What in particular? Would it matter at this stage, anyway?

vladkrack · 11-19-2002, 02:21 PM

You should have a defult route pointing to your network, without it you can't get out ...
What's the answer to:
# route

Thymox · 11-19-2002, 02:25 PM

For my working machine:

Code:

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.0.0     *               255.255.255.0   U     0      0        0 eth0
127.0.0.0       *               255.0.0.0       U     0      0        0 lo
default         192.168.0.1     0.0.0.0         UG    0      0        0 eth0

For my non-working machine:

Code:

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.0.0     *               255.255.255.0   U     0      0        0 eth0
127.0.0.0       *               255.0.0.0       U     0      0        0 lo
default         192.168.0.1     0.0.0.0         UG    0      0        0 eth0

As you can see, they are exactly the same, yet I can ping my gateway from this machine and yet I cannot from the other, and I can't ping eachother (i.e. 192.168.0.14 cannot ping 192.168.0.15, nor vice versa).

Thymox · 11-19-2002, 03:13 PM

OK, now I'm really annoyed! The damn thing just started working again!

Cheers anyway guys... feel free to throw your £0.02 equivalents into this melting pot as to why it stopped in the first place!

Thymox · 11-19-2002, 04:57 PM

Hehe! A little invasive surgery with a multi-meter has told me what the problem was - a loose connection on one particular RJ45 port on my switch. I've now swapped this particular cable over to another port and all is fine with out a hitch... for now