On Jun 6, Nathan E Norman wrote:
>
> ps. Between dmesg, ifconfig, and the proc filesystem you can poke
> around and get a good idea of what Linux thinks is going on, and how
> that meshes with what's supposed to be going on.
>
Thanks for the suggestions. I check with all these commands.
Here is the message I get from those programs. They all seems pretty
well.
dmesg:
NE*000 ethercard probe at 0x300 : 00 40 05 17 a9 a7
eth0: NE2000 found at 0x300, using IRQ 3
ifconfig:
eth0: Link encap 10Mbps Ethernet HWaddr 00 40 05 17 a9 a7
inet addr: 128.174.57.79 Bcast 128.174.255.255 Nmask 255.255.0.0
UP BROADCASTING RUNNING MULTICAST MTU: 1500 Metric: 1
Rx packets:0 errors: 0 drops: 0 overruns: 0
Tx packets:87 errors: 0 drops: 0 overruns: 0
Interrupt 3 Base Address 0x300
route:
Destination Gateway Genmask Flags Metric Ref Use Iface
128.174.0.0 * 255.255.0.0 U 0 0 5 eth0
127.0.0.0 * 255.0.0.0 U 0 0 2 lo
default 128.174.57.65 0.0.0.0 UG 0 0 9 eth0
/proc/net/arp:
IP address HW type Flags HW address Mask Device
128.174.57.65 0x1 0x0 00 00 00 00 00 00 *
The only abnormal thing is that 'Device' in file /proc/net/arp is null. And
when using 'route', it takes a long time to display the third row 'default'.
So, what is the cause for this? Actually, the LAN works all the time. IS
the configuration not correct?
-ctang
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] .
Trouble? e-mail to [EMAIL PROTECTED] .
