Linux - Wireless NetworkingThis forum is for the discussion of wireless networking in Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'm running FC5 (kernel 2.6.18-1.2257.fc5) on a Toshiba laptop. I've seen reference to this problem in other threads, but I was unable to find a solution.
My laptop has two cards: a regular cat5e connection, and a wireless card.
For FC5 and previous Linux distro installs (FC4 and others), the wired card has always come up as eth0.
For FC4 and previous distros, the wireless card was always identified as eth1.
However, since I've installed FC5, the wireless card is being given a new name on every boot (!). Instead of eth1, it's dev53418 or something (dev followed by 4-5 numbers).
The wirelss card works just fine, but the changing name makes it impossible for me to auto-configure the card at boot time.
Is there something I can do so that the wireless card is given a consistent device name on every boot?
Interesting. So perhaps hardware autodetection is causing this?
I've just tried that (chkconfig --levels 345 kudzu off) and rebooted a few times. I'm still getting a random device name for my wireless card (devXXXXX).
Distribution: RHEL/CentOS/SL 5 i386 and x86_64 pata for IDE in use
Posts: 4,790
Rep:
Sorry for the delay in getting back to this. I remember reading something a while ago (over a year) on this and the fix. I'm trying to find it again. If this is a new installation then please update to the latest or if possible install FC6 and then update.
this is usually udev related i think. try deleting your persistent.net.rules file in /etc/udev/udev.d (this file is automatically generated at boot, i suggest you just move it out the way initially and try a boot or restart udev)
It turned out to be a problem with the /etc/sysconfig/network-scripts files.
I'm not sure why, but FC5 at some point (right after install) decided to flip the order or names of the network cards. At some point my wireless card had been eth0, now FC5 wanted to call it eth1.
The ifcfg-eth0 startup script referred to the wireless card as eth0, and I'm guessing this mismatch was causing the devXXXX device names.
Once I swapped my ifcfg-eth0/1 files, the wireless card was properly named on boot (eth1 now). And as a result, I can configure it at boot time automatically.
Obviously a bug somewhere at boot. But there is a simple workaround (assuming the kernel doesn't want to keep flipping the names).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.