Actually, your problem probably is the eth0. The other NIC, eth1 is reporting oversize frames. It is telling you that something is passing it those frames. The thing that is odd, is that while eth1 is getting bad frames, eth0 is getting an unacceptable amount of collisions. It looks like the 2 are somehow looping back to each other. Check your port assignments on the hub. If you have one nic in the uplink, it could cause this - making eth0 and eth1 loop back to itself. Then, check your other machines. Make sure you didn't inadvertently assign another the same IP. I had this exact same error once, when I plugged the wrong cable into an uplink port on a hub. I had to reboot the host, and the clients, as the packet distortion hosed up almost everything on the LAN. Once I corrected the port assignment, and rebooted, everything was fine. (no more errors) If I understand correctly what your configuration is. You should have the adsl modem plugged into the uplink port, and the other (host and clients) plugged into the other ports. Also, with that bandwidth, consider a switch instead of a hub :) Ron --- Tyler <coolwheels@usa.net> wrote:

Below is an excerpt from my /var/log/messages file... this goes on and on and on, with no end... I don't understand why. The system is a Compaq DeskPro 5133 - P133 - 48MB EDO - 2 x 10/100 D-Link 538TX network cards - 4Mbit ADSL with 5 Static IP's. I am using this machine with TWO IP's off the ADSL on the same machine ... the ADSL is plugged into a 10/100 Hub, and then the computer(s) into the hub. This computer uses two IP's, so it can have two seperate hostnames. This problem only started when I added the second network card on the second IP address.. and the eth0 card doesn't seem to complain at all.. only the eth1 card complains. I run a Nameserver on the machine, and thats the ONLY thing I can think of that could be cuasuing some sort of "double" network traffic that is colliding or something.. yet ifconfig show's no collisions.. just a whole lotta errors & overruns on the eth1 card. yet all data flowing in/out on the eth1 card seems to do so without problem. PLEASE HELP ... hehe.. it doesn't seem to be affecting my network useage at this time, but it is annoying to get a 6 meg messages file within a few days... and the problem should be fixed anyways.

I am running SuSE 6.2 with some updates, including Bind is updated, and Kernel is 2.2.14, and many other miscelaneous updates.

11:18pm up 23 days, 15:50, 1 user, load average: 0.02, 0.10, 0.09 toybox /var/log# ifconfig eth0 Link encap:Ethernet HWaddr 00:80:5F:02:5B:5F inet addr:216.232.xxx.xx1 Bcast:216.232.xxx.xxx Mask:255.255.248.0 UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1 RX packets:6287661 errors:0 dropped:0 overruns:0 frame:0 TX packets:5234116 errors:0 dropped:0 overruns:0 carrier:0 collisions:19472 txqueuelen:100 Interrupt:5 Base address:0x7000

eth1 Link encap:Ethernet HWaddr 00:50:BA:85:EF:89 inet addr:216.232.xxx.xx2 Bcast:216.232.xxx.xxx Mask:255.255.248.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:132924 errors:555004 dropped:0 overruns:290947 frame:806805 TX packets:4 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 Interrupt:11 Base address:0x7200

lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:3924 Metric:1 RX packets:275253 errors:0 dropped:0 overruns:0 frame:0 TX packets:275253 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0

Sep 1 13:02:42 toybox last message repeated 8 times Sep 1 13:02:43 toybox kernel: eth1: Oversized Ethernet frame, status 815724fa! Sep 1 13:02:45 toybox kernel: eth1: Oversized Ethernet frame, status 815724fa! Sep 1 13:02:47 toybox kernel: eth1: Oversized Ethernet frame, status 74656e2e! Sep 1 13:02:47 toybox kernel: eth1: Oversized Ethernet frame, status 73646e6f! Sep 1 13:02:52 toybox kernel: eth1: Oversized Ethernet frame, status fe68e8d8! Sep 1 13:02:53 toybox kernel: eth1: Oversized Ethernet frame, status 815724fa! Sep 1 13:02:55 toybox kernel: eth1: Oversized Ethernet frame, status 2e637269! Sep 1 13:02:56 toybox kernel: eth1: Oversized Ethernet frame, status 6972746e! Sep 1 13:02:56 toybox kernel: eth1: Oversized Ethernet frame, status fe68e8d8! Sep 1 13:02:56 toybox kernel: eth1: Oversized Ethernet frame, status 1000608! Sep 1 13:02:56 toybox kernel: eth1: Oversized Ethernet frame, status ffffffff! Sep 1 13:02:57 toybox kernel: eth1: Oversized Ethernet frame, status 40ffff! Sep 1 13:03:01 toybox last message repeated 8 times Sep 1 13:03:02 toybox kernel: eth1: Oversized Ethernet frame, status 815724fa! Sep 1 13:03:03 toybox kernel: eth1: Oversized Ethernet frame, status 815724fa! Sep 1 13:03:06 toybox kernel: eth1: Oversized Ethernet frame, status 74656e2e! Sep 1 13:03:07 toybox kernel: eth1: Oversized Ethernet frame, status 73646e6f! Sep 1 13:03:11 toybox kernel: eth1: Oversized Ethernet frame, status fe68e8d8! Sep 1 13:03:13 toybox kernel: eth1: Oversized Ethernet frame, status 815724fa! Sep 1 13:03:15 toybox kernel: eth1: Oversized Ethernet frame, status 2e637269! Sep 1 13:03:15 toybox kernel: eth1: Oversized Ethernet frame, status 6972746e! Sep 1 13:03:15 toybox kernel: eth1: Oversized Ethernet frame, status fe68e8d8! Sep 1 13:03:16 toybox kernel: eth1: Oversized Ethernet frame, status 1000608! Sep 1 13:03:17 toybox kernel: eth1: Oversized Ethernet frame, status ffffffff! Sep 1 13:03:17 toybox kernel: eth1: Oversized Ethernet frame, status 40ffff! Sep 1 13:03:20 toybox last message repeated 8 times

__________________________________________________ Do You Yahoo!? Yahoo! Mail - Free email you can access from anywhere! http://mail.yahoo.com/ -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq