baselayout-12 + wpa_supplicant and HostAP problems [SOLVED]

guest · n00b Joined: 23 Jul 2005 Posts: 8

I'm using a Prism 2.5 card with updated firmware and hostap-0.4.7 loaded as the network driver. When the computer with this hardware first boots, everything works great. The problem is that, after hours of staying connected, it will run into problems that will eventually make it totally inaccessable remotely, and I start to see a flood of disconnected/connected messages in the system's logs like this:

UberLord · Posted: Thu May 18, 2006 1:46 pm Post subject:

Well, I can tell you that it's not a baselayout problem you've got it connected - once that's done baselayout is finished. I would guess it's a driver problem.
_________________
Use dhcpcd for all your automated network configuration needs
Use dhcpcd-ui (GTK+/Qt) as your System Tray Network tool

beatryder · Veteran Joined: 08 Apr 2005 Posts: 1138

Is there a man page for the new baselayout yet?

I have an issue with the network setup. I dont want it to bring up all my interfaces. In fact I would prefer it if my wireless only came on when I told it too.
_________________
Dont make it idiot proof, make it work.
Neucode.org
<suppressed key>

digitall2000 · Apprentice Joined: 21 Dec 2004 Posts: 267

well as far as i know just remove the wireless from the run level with rc-update
rc-update del <wireless> runlevel<boot-default>
the just bring it up by hand when needed

lance

UberLord · Posted: Thu May 25, 2006 7:27 pm Post subject:

beatryder · Veteran Joined: 08 Apr 2005 Posts: 1138

[quote=digitall2000]
well as far as i know just remove the wireless from the run level with rc-update
rc-update del <wireless> runlevel<boot-default>
the just bring it up by hand when needed
[/quote]

Thats what I had been doing, but I updated to baselayout-0.12 and it changed.

Ok well, I got it fixed now, but it seems like a lot more work than just "rc-update del net.eth1"
_________________
Dont make it idiot proof, make it work.
Neucode.org
<suppressed key>

guest · n00b Joined: 23 Jul 2005 Posts: 8

I'm not using the prism card anymore. I switched it with an ACX 111 based card with ndiswrapper, and it's working a lot nicer. One thing I did notice though is that wpa_supplicant leaves wpa_ctrl* files in the /tmp directory and doesn't remove them when it's finished. I was having problems with it and was getting "Socket already in use" messages while the system was booting followed by wpa_supplicant not starting correctly. Adding rm /tmp/wpa_ctrl* to local.stop fixed this problem, and now the system has wireless networking that doesn't keep dropping the connection.

guest · n00b Joined: 23 Jul 2005 Posts: 8

Ok forget that. Everything seems to be working ok now, but I do not recommend using ndiswrapper with an ACX111 based card. Most of the drivers that I tried with ndiswrapper appeared to work but I spent way too much time trying to figure out why the machine was spontaneously rebooting (8K stacks were enabled.) The acx driver seems to be more stable and is working with iwconfig. wpa_supplicant had some problems trying to communicate with the acx driver (couldn't set the ESSID correctly for some reason) so I'm no longer using it.