Suse 10.2: wlan0 keeps getting renamed eth0

xbennyboy · 12-23-2006, 12:00 AM

I have a bcm4306 wifi chip and got it installed on ndiswrapper. It works. However, I notice that during boot up, wlan0 keeps getting renamed to eth0. How do I prevent this from happening?

bigrigdriver · 12-24-2006, 01:15 PM

This is from SuSE documentation:

Quote:

Network

The wireless extensions must run before you try to configure the network based on these extensions. Apart from this, the wireless network does not differ from a wired network. You can run everything as you would in a normal network. Network cards have ordinary Ethernet names like eth0, and can also be normally addressed with tools like ifconfig or ip. Services like DHCP or similar can also be used. The only requirement is that the wireless extensions must be configured.

So, as long as it works, it doesn't matter what you call it. If it's a network card, SuSE will call it eth0.

xbennyboy · 12-24-2006, 01:52 PM

Haha. Of course. If it works, don't fix it. But I saw that Suse was renaming it for no apparent reason. Plus I am used to wlan0. Makes more sense.

Anyways, I figured it out. Type

Code:

vi /etc/udev/rules.d/30-net_persistent_names.rules

Then comment out or delete the rule that has eth0 in it.

Thanks for the help anyway, bigrigdriver.