baselayout-1.12.4-r2 breaks wireless

loisl

Hai all,

after upgrading to baselayout-1.12.4-r2 my wireless is broken on systems utilizing PCMCIA/Cardbus wireless cards driven by ndiswrapper (with build-in cards like ipw2100 everything is ok).

It does not matter if the card is plugged during boot-up or if it is plugged in sometimes later.

I am using a wpa_supplicant configuration wich worked perfectly with several previous versions of baselayout.

iwconfig shows that the card is perfectly associated with my access point, ifconfig shows, that it has no ip-address.

Running /etc/init.d/net.wlan0 (re)start manually does not work. The script complains that wpa_supplicant is allready running ...

After just running dhcpcd manually everything is ok.

I tried to play with the coldplug options in /etc/conf.d/rc, but this did not help at all.

Any suggestions and help is welcome.

Thanks,
Loisl

dalek · Posted: Sat Aug 12, 2006 1:14 pm Post subject:

Might look here.

https://forums.gentoo.org/viewtopic-t-488578-highlight-baselayout.html

May not be the same thing though.

_________________
My rig: Gigabyte GA-970A-UD3P mobo, AMD FX-8350 Eight-Core CPU, ZALMAN CNPS10X Performa CPU cooler,
G.SKILL 32GB DDR3 PC3 12800 Memory Nvidia GTX-650 video card LG W2253 Monitor
60TBs of hard drive space using LVM
Cooler Master HAF-932 Case

loisl · Posted: Sat Aug 12, 2006 6:34 pm Post subject:

Many thanks for the replay, but as i allready mentioned, playing with the hot/coldplug options in /etc/conf.d/rc does not work.

It is simply dhcpcd which is not called by the init script.

Loisl

kmarasco · Posted: Sat Aug 12, 2006 8:29 pm Post subject:

Similar problem. My previously working ndiswrapper configuration fails after upgrading baselayout yesterday. What's strange is that everything seems to be correct (valid ip address, iwlist wlan0 scanning seems fine, lease is assigned by router) but no connection. My hardwired eth0 works fine.
_________________
Just as choice in software is critical, so is choice in education. Power to the people. Kill the monopoly by privatizing U.S. K-12 schools.

kmarasco · Posted: Sat Aug 12, 2006 8:39 pm Post subject:

Well, wlan0 is working, but not as expected. If I stop my hardwired eth0 ( /etc/init.d/net.eth0 stop) then wlan0 works fine. Unfortunately they are not working simultaneously, meaning that if I unplug my ethernet cable while both interfaces are running, wlan0 does not function. I'm wondering if the baselayout change fixed a security issue that has revealed errors in my network setup.
_________________
Just as choice in software is critical, so is choice in education. Power to the people. Kill the monopoly by privatizing U.S. K-12 schools.

loisl · Posted: Tue Aug 15, 2006 7:23 pm Post subject:

No change of behaviour with baselayout-1.12.4-r2 and net-misc/dhcpcd-2.0.5-r1

Teiresias · n00b Joined: 07 Jun 2005 Posts: 6

Hi I had some problems with my net.eth0 after upgrading to the newest baselayout. Found out that there were some changes to the /etc/conf.d/net file. Maybe you are having the same problems ?

Narciso · n00b Joined: 22 Aug 2003 Posts: 11

I'm having the same problem; the interface starts, wpa supplicant authenticates successfully to my access point but dhcpcd does not run. I think I've tracked down the problem to the script /lib/rcscripts/net/wpa_supplicant.sh
It seems that the function wpa_supplicant_associated() does not work correctly, it fails to recognize that wpa_supplicant did its job successfully; I noticed that if I set associate_timeout_eth1=10 the startup script says:

# /etc/init.d/net.eth1 start
[...]
* Starting wpa_supplicant on eth1 ... [ ok ]
* Starting wpa_cli on eth1 ... [ ok ]
* Waiting for association [ ok ]
* Failed to configure eth1 in the background [ !! ]
* WARNING: net.eth1 has started but is inactive

If I do not define associate_timeout_eth1=10 all I get is:

* Starting wpa_supplicant on eth1 ... [ ok ]
* Starting wpa_cli on eth1 ... [ ok ]
* Waiting for association [ ok ]
* Backgrounding ...
* WARNING: net.eth1 has started but is inactive

wpa_cli -i eth1 status says that eth1 is correctly associated and issuing dhcpcd eth1 gets me an IPv4 address; the interface also automatically learns and IPv6 address from my router.

Thanks!

UberLord · Posted: Wed Aug 16, 2006 8:18 am Post subject:

Sounds awfully like this bug

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

Which is a portage bug and not baselayout - basically ensure that the interface can be brought up.
_________________
Use dhcpcd for all your automated network configuration needs
Use dhcpcd-ui (GTK+/Qt) as your System Tray Network tool

Narciso · n00b Joined: 22 Aug 2003 Posts: 11

That was it, UberLord, thanks a lot!

-Biker