Emerge -uvD world broken my wireless network [solved]

Message

cdstealer · Post by **cdstealer** » Sat Aug 12, 2006 7:36 am

Hi,
Ran an update and the networking on my laptop no longer works. I think it my have something to do with baselayout but going back to the original version doesn't solve anything.
eth1 (wireless) just won't come up and after various tweaks to get it working now complains about

Code: Select all

Error for wireless request "Set Encode" (8B2A) :
    SET failed on device eth1 ; Operation not supported.
 *   eth1 does not support setting keys
 *   or the parameter "mac_key_wififukka" or "key_wififukka" is incorrect
 *   Failed to configure wireless for eth1                                  [!!]

Has anyone come aross this yet?
Forom what I have read, baselayout may be the reason.
Current baselayout version is "baselayout-1.12.4-r1" updated from "baselayout-1.11.15-r3"

If you need anymore info or config files.. just ask...

GenesysGen2 · Post by **GenesysGen2** » Sun Aug 13, 2006 7:32 am

Ditto on my server.

I think the fault is in /etc/init.d/net.lo somewhere, but I can't work out where.

I tried rolling that script back to the previous version, but it complained that
/lib/rcscripts/net.modules.d/helpers.d/functions no longer exists...

Unfortunately I can't (easily) get the info off the server, but dmesg doesn't appear to give any meaningful output anyway.

running /etc/init.d/net.ra0 start gives something like:

Code: Select all

* Starting ra0
*    Configuring wireless network for ra0
Error for wireless request "Set Mode" (8B06) :
    set failed on device ra0 ; Network is down.
*  ra0 does not support setting the mode to "managed"
Error for wireless request "Set Mode" (8B06) :
    set failed on device ra0 ; Network is down.
*  ra0 does not support setting the mode to "managed"
Error for wireless request "Set Encode" (8B2A) :
    set failed on device ra0 ; Network is down.
*  ra0 does not support setting keys
*  or the parameter "mac_key_WAN" or "key_WAN" is incorrect
*  Failed to configure wireless for ra0

It's especially painful because the wireless connects the server to the internet...

Running baselayout 1.12.4-r2

dsegel · Post by **dsegel** » Sun Aug 13, 2006 3:34 pm

Did you update anything else at the same time as baselayout (like your kernel)?

Did you run the commands at the end of the baselayout emerge to symlink the net.eth* scritps to net.lo?

AYBABTU · Post by **AYBABTU** » Sun Aug 13, 2006 4:16 pm

Same problem here.

cdstealer · Post by **cdstealer** » Sun Aug 13, 2006 4:37 pm

HI dsegel
On the original update I didn't update the symlinks.. I just switched off the laptop and went to bed without reading the screen and then didn't hit the problem until the following morning. My own fault. There were about 12 updates, the kernel wasn't one of them. I've been running 2.6.17-r4 since it hit portage. I've unmerged and re-merged baselayout and then ran the updates needed configs and symlinks. I've deleted all the net.* files and let baselayout re-create them, however, it doesn't create a net.eth1 for the wireless. I created a new symlink to net.lo and called it net.eth1 and thats where I get the error message when bringing up the device. I feel as though I may have just ansered my own question... I'll re-create the net.eth1 the old way then I'll edit this post with the result.

AYBABTU · Post by **AYBABTU** » Sun Aug 13, 2006 4:41 pm

ok, solved. that was a bug of baselayout.

try

Code: Select all

emerge =sys-apps/baselayout-1.11.15-r3

cdstealer · Post by **cdstealer** » Sun Aug 13, 2006 5:28 pm

HI,
AYBABTU.. already tried that.. still the same.

Re-created the net.eth1 file (not as a symlink) and still the same. Time to RTFM on wireless and re do from scratch.. maybe I'll find the answer as to why it all went tits up?

With baselayout-1.11.15-r3 I now get

Code: Select all

 * Caching service dependencies ...
 * Starting eth1
 *     (iwconfig) is not a valid module (missing provides)

dsegel · Post by **dsegel** » Sun Aug 13, 2006 6:54 pm

That still sounds like the init scripts are doing something wrong. Try loading the wireless drivers manually and then using ifconfig to configure the port, like this:

ifconfig eth1 192.168.1.1 netmask 255.255.255.0

cdstealer · Post by **cdstealer** » Sun Aug 13, 2006 7:07 pm

Getting there... took a look a /etc/conf.d/net and found my config entries had been adjusted. Corrected these and restarted eth1.. it had put extra quotations outside of the brackets. The device now comes up but will not see my router.

This is my net file

Code: Select all

modules=("!iwconfig")
config_eth1=("192.168.1.2 netmask 255.255.255.0")
routes_eth1=("default via 192.168.1.1")

I'll try the manual command and see what happens

manual still does not work..

checked my /etc/conf.d/wireless and read the net.example and wireless.example for any changes. Made sure my ipw2200, ieee80211, ieee80211_crypt & ieee80211_srypt_wep modules were loaded.

/var/log/messages seems to report everything loading ok with no errors.

It looks like now it's just case of getting the thing to accept my wep settings...

iwlist doesn't anything either

** EDIT ** I have removed all security from the router and enabled DHCP.. still nothing.. still can't see the router

Went back (again) to baselayout-1.11.15-r3 and iwlist works again and I can see the router when I scan.. still can't connect though.

** EDIT ** YAY... sorted.. changed modules=("!iwconfig") to modules=("iwconfig") and wireless is now working again with WEP.

summary:

baselayout-1.11.15-r3
modules ipw2200, ieee80211, ieee80211_crypt & ieee80211_crypt_wep loaded

/etc/conf.d/net

Code: Select all

modules=("iwconfig")
config_eth1=("192.168.1.2 netmask 255.255.255.0")
routes_eth1=("default via 192.168.1.1")

/etc/conf.d/wireless

Code: Select all

mode_eth1=Managed
channel_eth1=6
essid_eth1=*********
key_*********=********************

Dunno what to do about baselayout... I suppose if it ain't broke don't fix it. Thanx to you for your help.