On 6/13/05, Richard Fish <[EMAIL PROTECTED]> wrote: > Danny Luker wrote: > > >Hi all, > > The other night I did an emerge sync; emerge world -vu and got a > >new and improved version of baselayout. I screwed up and let > >etc-update clobber all my config files (stupid I know ;() ... anyway, > >I've recovered from it except I can't get wireless working. It all > >was so simple before. Even doing it manually was simple but I can't > >get it to connect (associate) with my access points. Before all this > >I could do it manually by: > > > ># modprobe ath_pci // using the madwifi drivers on my Thinkpad T40 > ># ifconfig ath0 192.168.1.53 netmask 255.255.255.0 up > ># route add default gw 192.168.1.1 ath0 > > > > > > > > Well, nothing in the new baselayout should have prevented your ability > to bring things up manually. The only thing I can think of that you > might be missing is an "iwconfig ath0 essid 'any'" command. > > For bringing things up automatically, the following lines in > /etc/conf.d/net should work: > > modules_ath0=( "ifconfig" "iwconfig" ) > config_ath0=( "192.168.1.53 netmask 255.255.255.0" ) > routes_ath0=( > "default via 192.168.1.1" > ) > > If you need encryption, you will also need to configure > /etc/conf.d/wireless appropriately. Take a look at > /etc/conf.d/net.example and wireless.example. > > If this doesn't help, please post your /etc/conf.d/net and wireless > files. And also exactly what happens when you try to bring up the > interface manually. > > -Richard > > -- > [email protected] mailing list > >
Thanks Richard, I have since made progress in the area of manually
bringing up wireless. I discovered, after much experimentation, that
I can get my interface to play well by giving it the following:
iwconfig ap off
and then proceding with ifconfig and route as normal. Still can't get
it to do it automatically. And, like you, I don't understand why the
base layout change would cause me to have to issue the above command
when I never had to in the past. So, after putting the text in
/etc/conf.d/net you suggested I get the same results. I tried adding
the "ap off" in the /etc/conf.d/wireless iwconfig_ath0 variable ...
didn't work. Tried a little preup() function to issue the "iwconfig
ap off" command ... didn't work ... well at least I can do it manually
now ;)
As for what it does ...
* Starting ath0
* Loading networking modules for ath0
* modules: iwconfig essidnet iptunnel ifconfig dhcpcd apipa
* iwconfig provides wireless
* ifconfig provides interface
* dhcpcd provides dhcp
* Running preup function
iwconfig ath0 ap off
* Configuring wireless network for ath0
* Connecting to "any" (WEP Disabled) ...
[ !! ]
* Failed to configure wireless for ath0 [ !! ]
/var/log/messages gets an entry ...
Jun 13 04:27:49 localhost rc-scripts: Failed to configure wireless for ath0
and nothing else very interesting happens ... I wish there were more
info ;) Maybe I just do know where to look .. ;(
I've attached the net and wireless config files.
Thank you for taking time to look at this ... really has me scratching my head.
Danny Luker
net
Description: Binary data
wireless
Description: Binary data
