On 02/02/11 08:59, Jean H. Theoret wrote: > This one's got me stumped for a few days now... > > How is it possible to control the network interface numbering assignment > order?
barely. > Here's my specific case: the box has 2 on-board Ethernet interfaces and > a 3rd one on a PCI-Express card. They come up as: > > re0: PCI-Express card > re1: on-board interface #1 > re2: on-board interface #2 > > A recent event had disabled the PCI card, and the remaining network > interfaces ended up being reassigned (upon the next reboot, of course) as: > > re0: on-board interface #1 > re1: on-board interface #2 > > Could this have been prevented by forcing network interface assignment > to on-board interface _first_, then the PCI card? Your problems would have changed. IN YOUR CASE, it may have changed from a problem you weren't ready for to a one you were, but you didn't eliminate the problem. > Or is there a way to > bind network interface assignment to the adapter's MAC address as > numbering hint? Give it a chance and I think you will start to see where the OpenBSD system is a lot easier. Yes, when things change in the system, things change in your config, which can cause breakage. OpenBSD's device numbering system is somewhat simplistic, which means it has simple problems which are easy to fix. Having worked with similar problems (and their recovery) on other OSs...ick. A much better solution to your original problem would be to have spare parts on hand enabling you to replace the failed re0, in which case you would have NOTHING to change, ANY screwdriver literate tech could fix your system and bring it back up without any reconfiguration, and no sharing of an admin PW (or walking someone through vi over the phone). Nick.
