On 3/20/2013 11:38 AM, Per Jessen wrote:
Robert Schweikert wrote:
On 03/20/2013 02:07 PM, Marc Chamberlin wrote:
I have had this happen before, but unfortunately I don't remember how I solved it.... I am installing openSuSE 12.3 on a gateway server with 2 NICs. Somehow, somewhere openSuSE/YaST gets the device names I want to assign to each NIC (eth0 and eth1) backwards, and I need to reverse the assignments. I have tried the obvious approach of going in to YaST -> Network Devices -> NetworkSettings -> Overview, select the NIC card and edit it, go to the Hardware tab and change the device names. If I try to simply change, for example, eth0 to eth1, it confuses YaST when it sees two devices with the same name, in this case 2 eth1 devices. (even though I plan to change the other NIC's device name shortly.) So I tried a different approach, change eth0 to eth2, eth1 to eth0, and then eth2 to eth1. On the surface that seems to work, according to YaST, but the network remains unusable and from logs and other indications I believe that YaST is not doing a thorough job of changing device names where necessary. I can see log messages showing communication attempts that is going on over the network which is indicating that communication attempts is still being done via the wrong NIC/device. (Wireshark confirms this also.)
A question I might ask, if I delete all the network devices in YaST, and start over with setting them up, YaST by default assigns the device names to each NIC but as I said opposite to what I want. Where/how does YaST get this initial assignment of device names for each NIC? Is there somewhere I could go, underneath, and reconfigure manually the device names? (I have done some hunting around via grep, searched all through /etc for example, and no joy finding a magic config file....) Devices and their names are handled by the kernel via udev. YaST gets its information from udev and displays the "truth", i.e. the way the kernel handles the devices.
If you need to modify this you will need to create a udev rule that meets your needs. Then place the the rules in /etc/udev/rules.d. Network overrides are stored in the rule:
70-persistent-net.rules
Hmm, something changed in 12.3, see https://bugzilla.novell.com/show_bug.cgi?id=809843
Oh boy! Thanks Per Jessen for the pointer to that bug report. Looks like the guru's are on top of it and chasing this problem down. My question now becomes this - For those of us with an impaired network under 12.3 how do we get the fix for this bug when it becomes available? Do we have to download a new ISO file/DVD for openSuSE12.3 and reinstall from scratch? Hopefully this fix will be available soon, (how will I know?) and again for the record I wish the openSuSE designers would give some thought on how we are suppose to set our systems up so we can regress back to a previous version of openSuSE when upgades go wrong or take a long time to complete.... Marc... -- "The Truth is out there" - Spooky -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org