Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
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 was going to post this in the hardware forum, but I thought this might be more appropriate. I have a wireless USB interface that I have configured in Redhat 9. It works perfectly without WEP enabled. With WEP enabled, it can't communicate with my wireless router on bootup, even though I have my ifcfg file altered with the settings for my network.
At first I had a problem with the MODE option in my ifcfg file. My wireless device won't accept that option, and it comes back with a segmentation fault. At any rate, after I fixed that by editing the ifcfg file, I still couldn't get the network to work. Finally, I discovered that if I execute "iwconfig eth0 key on" and then do "ifup ifcfg-eth0" (which is my wireless interface) everything works.
So the question is - how can I automate this? I would assume there's something I can put in my ifcfg file that would do this automatically, correct? If so, what would that be? If not, how should I run the first command on boot up?
The syntax is:
KEY=12345abcdefg ...
Enter that in /etc/sysconfig/network-scripts/ifcfg-ethx and you should be able to avoid having to set the WEP key every time you reboot.
I know that, and I already have that in the file and it's working fine. My problem is that I need to be able to run the "iwconfig eth0 key on" command. Just having KEY=xxxxxxxxxxxx in there for some reason doesn't work with my wireless device. I have to specifically run "iwconfig eth0 key on" before I run "ifup ifcfg-eth0".
Maybe I'll post a copy of my ifcfg file because I might have something else messed up.
As I mentioned above, this will let me connect to my network as long as I run iwconfig first. I'm wondering if this is caused because I can't have a MODE=whatever line in my ifcfg file. Any ideas?
Thanks for any help, even if you just read this and don't know the answer.
(I wish I had my RH drive installed to check, but I'm running Slack this AM.)
Maybe a conflict with the channel and the mode setting. Try deleting the channel entry and setting MODE=managed or auto.
Hi again,
I'll give that a try and see what happens. I tried executing iwconfig with the mode command before and got the same segfault, though. But hopefully it'll work differently.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.