I do not understand the use of the /etc/conf.d/wireless file

MasterX · Veteran Joined: 26 Jun 2003 Posts: 1165

I have emerged baselayout-1.11.10-r7 and I am not able to make the wireless work. I have read the various threads for setting the wireless, but I do not think they solve my problem. I do not want to set an ESSID or a WEP. For the moment, all I want to do is to set the wireless so that I can connect to any network that is in range.

Before, with the old version of baselayout, I would turn on the wireless card, run kwifimanager,which will scan the wireless networks, connect to one of them and then by running "/etc/init.d/net.eth1 start" I will get the IP address.

Now, the wireless card has to be on when the system boots or else I get a bunch of messages in dmesg. If the wireless card is on, during boot, kwifimanager will be able to connect but as soon as I run "/etc/init.d/net.eth1 start" I will get the message "out of range". If the wireless card is off during boot, and I turn it on after I have logged into KDE, kwifimanager gives the message "out of range". Kwifimanager can scan the network and it will find all the available networks, but I cannot connect to them.

Since, I do not have a wireless router and it is not in my plans to build a wireless network, and the only thing I want to do is to test the wireless card what do I need to do to connect to any network?

Can I somehow disable to use of the script for the wireless during boot?

This is what I have in the /etc/conf.d/wireless

UberLord

MasterX · Veteran Joined: 26 Jun 2003 Posts: 1165

UberLord,

Could you give me some basic directions or even better could you the link for the docs?
I have read the article in Gentoo-Wiki, but it did not help.

UberLord · Posted: Mon Apr 18, 2005 3:23 pm Post subject:

http://dev.gentoo.org/~uberlord/net-book/

MasterX · Veteran Joined: 26 Jun 2003 Posts: 1165

MasterX · Veteran Joined: 26 Jun 2003 Posts: 1165

One last question. Does anybody know why during boot both net.eth0 and net.eth1 are started? Is it possible to control that and not start the net.eth1?

UberLord · Posted: Mon Apr 18, 2005 11:41 pm Post subject:

https://bugs.gentoo.org/show_bug.cgi?id=78495

jphelps · n00b Joined: 06 Nov 2004 Posts: 21

This may be the wrong place but I think I just need a little baselayout help: Is there a way to have baselayout do an 'ifconfig ath0 up' initially?

I have an orinoco gold a/b/g card. It will not associate with any type of AP using the latest baselayout package and the MadWiFi driver package. I believe this is due to the fact that an 'ifconfig ath0 up' is required just prior to setting up the iwconfig parms for this driver/card for it to associate with any AP If I do the following manually, it works fine:

ifconfig ath0 up
iwconfig essid 'whatever'
iwconfig enc stuff (if needed)
.. wait a few seconds (watch iwconfig ath0) until it scans and finds an AP
dhcpcd ath0

And life is good. If you omit the ifconfig up it never works. I am at a loss on how to proceed to debug/fix this. Any suggestions would be appreciated.

UberLord · Posted: Wed Apr 20, 2005 9:30 am Post subject:

jphelps · n00b Joined: 06 Nov 2004 Posts: 21

Hm, I thought I was not interpreting the NET_DEBUG run I did of the net.ath0 script. Bummer. I have no idea what's going on either. Maybe it's a specific combination of events that's causing my card to choke.

In any event, I forgot to mention wpa_supplicant does seem to work OK as you also suggested. That's also probably the way to go anyway but I thought I'd ask. Thanks for your info. If I get some time, I'll dig some more.

UberLord · Posted: Thu Apr 21, 2005 5:59 am Post subject: