Bugzilla – Bug 105905
Unable to configure second net card
Last modified: 2005-12-27 21:35:31 UTC
Trying to configure second nic through yast, Hi-light second card -- select edit -- Network address setup -- configuration name is same as configured eth0 First Card -- Dell Netxtreme Gigabit Second Card -- RealTek 8139
Please provide YaST2 logs and hwinfo output, see: http://www.opensuse.org/index.php/Bug_Reporting_FAQ#YaST
Cannot fix it without any logs or other response...
Resolution: WORKSFORME it is pretty stupid. There is no errors in the logs. Problem is with with DNS resolution. setting up activation of secondary NIC will disable name resolution. LAN works fine with two cards (e.g. if samba rely on lmhosts). eth0 RX packets:95 errors:0 dropped:0 overruns:0 frame:0 TX packets:158 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:14399 (14.0 Kb) TX bytes:19957 (19.4 Kb) Interrupt:193 eth1 RX packets:0 errors:0 dropped:1179630 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) see a difference? when only one card is up, everything works (any card). Activating secondary card kills internet (DNS problems becasuse all packets are dropped and for some reason it resuses to connect through the other card) but LAN works (samba has specified interface and lmhosts for name resolution). Shutting down firewall changes nothing. The only error in the logs is ntp timeout (obviously but strange: service is attached to both cards: eth0 and eth1). so "worksforme" solution is worthless. this worked well winth suse 9.2 and stopped with 9.3. still does not work with 10.0 system: SuSE 10.0 OS 64-bit NIC: Linksys NC100 onborad NICs: Giga-byte CK8S Giga-byte Marvell 88E8001 each of the above works well if only one NIC is activated /etc/hosts lists all interfaces /etc/resolv.conf lists DNS servers only and search domain. Upon activation of second NIC Yast Network device module becomes ex tremerly slow (trying to connect). this issue is not resolved