From:
On Sunday 22 January 2006 21:38, Richard Atcheson wrote:
On Monday 23 January 2006 12:06 am, david rankin wrote:
Do I go to a straight ifcfg-eth0 and ifcfg-eth1 setup in /etc/network/sysconfig? Do I put both eth-id-00:4c:69:6e:75:79 and eth-id-00:04:5a:87:c8:43 in there (seems like a lame Band-Aid approach)
What is the best way to solve this conundrum???
When it is working and not working what does ifconfig say?
Two things I would try. 1st, make sure there is only one nic setup in Yast. 2nd, I would swap out the nic.. Might have a flakey card.
Since it's a new machine, is it possible there is an onboard nic and a card installed as well?
Richard Somehow your software thinks there are more than one nics. Double check that your motherboard does not have a second nic. if you find one, disable it in the cmos setup. When there is just one, suse stops being confused. That has been my experience with 10.0. 9.3 had the problem as well, but once set in Yast it could handle it. What happened to the days when one could assign eth0, eth1 and so one to particular cards I don't know. d.
Guys, when I said it was a new box, I misspoke. It is new to my home, but it is the same box that worked flawlessly for the past 5 years at work as a server running mandrake 7.2. Nothing has changed and there is only one NIC. Yast only sees 1 NIC. Ifconfig shows: nemesis:/home/david # ifconfig eth1 Link encap:Ethernet HWaddr 00:04:5A:87:C8:43 inet addr:192.168.6.16 Bcast:192.168.6.255 Mask:255.255.255.0 inet6 addr: fe80::204:5aff:fe87:c843/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:5399 errors:0 dropped:0 overruns:0 frame:0 TX packets:3781 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:555501 (542.4 Kb) TX bytes:703613 (687.1 Kb) Interrupt:11 Base address:0xec00 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:3191 errors:0 dropped:0 overruns:0 frame:0 TX packets:3191 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:239728 (234.1 Kb) TX bytes:239728 (234.1 Kb) It is as if eth0 just dissapeared into oblivion.. Any more guesses?? Maybe the PCI bus is randomly loading the card in a different order some times?? -- David C. Rankin, J.D., P.E. RANKIN LAW FIRM, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 (936) 715-9333 (936) 715-9339 fax www.rankinlawfirm.com --