Making networking more robust under SuSE 9.3 under Virtual PC

Making networking more robust under SuSE 9.3 under Virtual PC

  • Comments 6

I do not know when this happened - but in the last couple of releases of SuSE Linux they have taken a weird dependency on the MAC address of the network card.  To be precise - once you have configured your network card under SuSE - changing it's MAC address will cause SuSE to not initialize that network card (unless you remove and reconfigure it through YAST).

This is quite painful because - as I outlined here - Virtual PC can and will change the MAC address of the virtual network card from time to time.  And in my case (as I regularly move my virtual machines between Virtual PC and Virtual Server on different physical computers) the MAC address is getting changed almost constantly.

Thankfully there is a relatively easy (though not intuitive) way to solve this.  What you need to do is to get to a command prompt and type in the following commands:

  1. cd /etc/sysconfig/network

  2. ls

    At this stage you should see a file called 'ifcfg-eth-id-00:03:ff:xx:xx:xx' (substitute the 'xx:xx:xx' appropriately).  This is the cause of the problem.

  3. sudo mv ifcfg-eth-id-00\:03\:ff\:xx\:xx\:xx ifcfg-eth0

    Once again you should substitute the 'x's appropriately

Once you have done this you should be able to reboot the virtual machine and have the networking continue to work no matter what the MAC address is of the virtual network card.


Leave a Comment
  • Please add 1 and 1 and type the answer here:
  • Post
  • Could you explain under which circumstances VPC changes the MAC?
  • Jss - just follow the link in the original post.

  • My fault, thanks a lot!

    I was a bit confused by the initial statement but the reasons given in the link are quite obvious.

    Thanks again!
  • If a real machine has more than one network adapter then you very likely want to set different firewall rules for each network adapter. SuSE felt the MAC address provided a sufficiently unique identifier by which to distinguish one network adapter from another (wonder where they got that idea). The IP address would be sufficiently unique for many of these purposes, but still, when the machine boots up you want to make sure that each network adapter gets assigned the IP address that was intended for it instead of having them swapped around. What other kind of key do you suggest using instead?
  • Hi Norman,

    Most OSes use a combination of Hardware ID / PCI slot / PCI function ID.

  • I am trying to instal Suse Linux 9.3 and I keep getting

    <0> Kernal panic - not syncing" Attempted to kill idle task! no cont in shutdown!
Page 1 of 1 (6 items)