Re: ethernet configuration
On Fri, Sep 17, 1999 at 08:50:42AM -0700, Stephen Monroe wrote:
> my /etc/init.d/network file contians:
> #! /bin/sh
> ifconfig lo 127.0.0.1
> route add -net 127.0.0.0
This is the so called loopback device which is available on EVERY ip connected
machine. Your ethernet is called "eth0" not "lo" ...
> The lights on my card are actually lit up and blinking,(supposedly showing
> data transmission, I think) but I can't ping any servers or anything.
Normal - You initialized your "loopback" interface perfectly. Means you
are able to reach yourself ...
> eth0 Link encap:Ethernet HWaddr 00:20:AF:EE:05:45
> inet addr:126.96.36.199 Bcast:188.8.131.52 Mask:255.255.254.0
> UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:24783 errors:1 dropped:1 overruns:0 frame:1
> TX packets:11598 errors:0 dropped:0 overruns:0 carrier:0 coll:96
> Interrupt:10 Base address:0x300
> My init addresses seem correct, except I don't have a "Bcast" address.
You MUST have a broadcast address - This one might be wrong but it looks
not THAT bad.
> Also, at bootup I know Linux recognizes my card "eth0" and it starts the
> DHCPcd. The driver for my card is "Tulip," which it also recognizes.
When you are doing DHCP in your network environment this should all be
Please have a look at your routingtabe (netstat -rn) and try to ping
the destination for your network "0.0.0.0" (default)
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
0.0.0.0 192.168.0.1 0.0.0.0 UG 0 0 0 eth0
This one ...
Florian Lohoff email@example.com +49-5241-470566
... The failure can be random; however, when it does occur, it is
catastrophic and is repeatable ... Cisco Field Notice