On Wed, Aug 02, 2006 at 01:50:28PM +0200, Beau Olivier wrote:
Hi,
yes, this is interesting, and i think it points out a new problem, 802.1q on nics :
eth1 Link encap:Ethernet HWaddr 00:0D:9D:4E:11:9C
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:2798842 errors:0 dropped:0 overruns:0 frame:0 TX packets:8950695 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:217776970 (207.6 MiB) TX bytes:4275403340 (3.9 GiB) Interrupt:201eth1.9 Link encap:Ethernet HWaddr 00:0D:9D:4E:11:9C
inet addr:192.168.250.33 Bcast:192.168.250.0 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:2226941 errors:0 dropped:0 overruns:0 frame:0 TX packets:3441485 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:520111630 (496.0 MiB) TX bytes:410431496 (391.4 MiB)
Perhaps, but these data should not get anywhere near the code that prints out this message. The code that generates that message is the one that parses the output from "netstat -s" which should look like
Ip: 3017099 total packets received 1 with invalid addresses 0 forwarded 0 incoming packets discarded 3017058 incoming packets delivered 3154813 requests sent out Icmp: 51081 ICMP messages received 0 input ICMP message failed.
What does this command report on your host?
Regards, Henrik