-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday 26 November 2002 04:03 am, Mike Burger wrote: > Ethernet collisions. They're unavoidable...the nature of Ethernet > makes it so, but the frequency of collisions is low enough to not cause > you worry.
> > eth1 Link encap:Ethernet HWaddr 00:50:BF:94:BD:D1 > > inet addr:192.168.10.1 Bcast:192.168.10.255 > > Mask:255.255.255.0 > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > RX packets:569985 errors:70 dropped:0 overruns:0 frame:74 > > TX packets:0 errors:161464 dropped:0 overruns:0 > > carrier:319669 collisions:0 txqueuelen:100 > > RX bytes:55468243 (52.8 Mb) TX bytes:0 (0.0 b) > > Interrupt:5 Base address:0xa000 > > What my question is why my eth1 get an errors :70 & TX bytes:0 ? That explains the RX errors, but look at the TX errors. TX packets:0 errors:161464 Something's very broken, I'd guess. Firewall rules perhaps, assuming the network device is working properly? - -- - -Michael pgp key: http://www.tuxfan.homeip.net:8080/gpgkey.txt Red Hat Linux 7.{2,3}|8.0 in 8M of RAM: http://www.rule-project.org/ - -- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE942NQn/07WoAb/SsRAj9FAJ4rTXZh8aJwhNOJlvC810U0jvRU7gCdGNVT OSYSCASSGCf2zABVkfy4kKA= =zW5h -----END PGP SIGNATURE----- _______________________________________________ Seawolf-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/seawolf-list
