Thank you. syslog is fine, I used ifconfig and here is the result. So it is obvioulsy something wrong at RX. Is
there a way to dig into eth0 driver and see why it drops packet?
After transfered a 45MB file to the laptop in LAN
eth0 Link encap:Ethernet HWaddr 00:60:6E:AA:0E:A9
inet addr:192.168.7.101 Bcast:192.168.7.255 Mask:255.255.255.0
inet6 addr: fe80::260:6eff:feaa:ea9/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:19948 errors:0 dropped:0 overruns:0 frame:0
TX packets:36465 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1239726 (1.1 MiB) TX bytes:47820580 (45.6 MiB)
After trying to connect to
www.cnn.com
eth0 Link encap:Ethernet HWaddr 00:60:6E:AA:0E:A9
inet addr:192.168.7.101 Bcast:192.168.7.255 Mask:255.255.255.0
inet6 addr: fe80::260:6eff:feaa:ea9/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:20127 errors:16 dropped:8 overruns:0 frame:8
TX packets:36552 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1272239 (1.2 MiB) TX bytes:47830710 (45.6 MiB)
Quote:
Originally Posted by MS3FGX
Using ifconfig, do you see any errors or dropped packets? What about in the syslog, any strange errors from the kernel?
|