Tyler, just some thoughts.....
Have you tried replacing (eth1) card with another model/brand? Could it actually be the wrong driver for the card? I found it a bit strange that both cards are the same D-Link model but
Good eye... hehe.. I was writing this very late tonight, and its even later
now :-/ ... you are correct, the eth0 is an integrated Compaq 10/mbit
card... thats the one not having any problems according to the logs, and the
secondard card, is the D-Link 538TX 10/100 NIC... the driver is the correct
one... it is supposed to use the RealTek 8139 driver. and I have probably
about 5-10 of these cards in other machines, including linux & windows
95/98/2000 ... all without problems. Windows 2000 first recognizes it as a
8139, then when you run web update, it finds a newer driver, and renames it
to D-Link. however, the linux machines just use the 8139 driver.
----- Original Message -----
From: "Michael Doerner"
MAC addresses show different vendors? (Or you might have changed eth0's hardware address?). Due to (http://standards.ieee.org/regauth/oui/index.shtml), the eth0 card (00-80-5F) should be a Compaq card, eth1 (00-50-BA) a D-Link model?
Regards, Michael Doerner -----Original Message----- From: Tyler [mailto:coolwheels@usa.net] Sent: Sunday, 3 September 2000 18:27 To: suse-linux-e@suse.com Subject: [SLE] Problem with two Network cards in System
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! .... cut...
-- 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
participants (1)
-
coolwheels＠usa.net