Hrm, ndiswrapper works fine but the netcfg2 scripts fail? Is this correct?

Yes, I suppose, but they were working fine until I upgraded from 49. I upgraded once before to v. 50 but the scripts stopped working so I downgraded back to 49. But no my cache is cleared out so thats no longer an option. I just thought that since they worked fine till I upgraded, it must be a problem with the upgrade.

It's not a netcfg2 problem, it's been common on the forums. Even manual connection hasnt been working.

I can connect manually to an unencrypted network, without using the netcfg2 scripts.

Hrm. ok.

What output do you get from netcfg2?
Post your netcfg2 config (attach or pastebin)
Will netcfg2 also connect to the unencrypted network?

Could it have been a kernel update, or is it definitely ndiswrapper? netcfg2 hasnt changed, and the ndiswrapper changelog doesnt show anything significant.

The output I get looks like this:

:: networkname up - Wireless association failed [FAIL]

and here is my netcfg2 profile

CONNECTION="wireless"
INTERFACE=wlan0
SCAN="yes"
SECURITY="wpa"
ESSID="networkname"
KEY="***********"
IP="dhcp"
TIMEOUT=20

As far as what broke it.. I have no clue. The kernel was giving me an issue so I reinstalled it and the issue resolved itself.

Scratch that close request. It crapped out on me again...

Ok. Set WPA_OPTS="-dd"

Also, please try an unencrypted network.

And also check... what kernel versions, do some work, do others not?

Okay.. it just started working again.. I'll wait a few hours or days and see if it breaks again.

It started getting flaky after ndiswrapper 1.49. So that was kernel 2.6.28.8-*?

2.6.23.8-* rather..

I can connect to unencrypted and the encypted broke again...

when it's broken, try setting WPA_OPTS="-dd" and see what output it gives you.

It says Daemonize... - wireless association failed. I extended the timeout to 60, but still no dice

oh ok, try WPA_OPTS="-dd &> /tmp/wpa_log" then post /tmp/wpa_log (attach or pastebin.archlinux.org) -- don't worry, your wireless key wont be in it.

It is still dumping the daemonize message to the command line. but It wasn't working then I cleared out all the temp wpa.* files (wpa.8oaOUE098 etc...) that it started working. Could these files have something to do with it?

which daemonize message?

those temp files shouldnt make any difference at all.

Given the erratic behaviour here... you sure your wireless reception is fine?

the daemonize line appears like this:

# netcfg2 home_mynet54g
:: home_mynet54g up [BUSY]
Daemonize..

Then falls back to the single line
:: home_mynet54g up [FAIL]

any more thoughts on this? I still cant connect to an encrypted network but an unencrypted network is fine.

I'm sure it's a driver problem.

- I havn't changed wireless connection code for months
- No other reports, no other drivers
- Problem is intermittent
- ndiswrapper is involved
- ndiswrapper has been updated

the daemonise message is wpa_supplicant being err... verbose because I suggested WPA_OPTS="-dd" -- though that wont work as it's getting daemonised. I'll add some debugging options to the next netcfg so we can get more info.

I'll go with what James said here. ndiswrapper is crap a lot of the times. It may work on every else's machine except yours. The only option is to use an older version and wait for a newer one. Such is the pain of these closed-source wrappers.

It's also best if you report this upstream so they know.

Has this been reported upstream or solved?

No. I actually got a new laptop, and haven't put WPA back on my access point yet. I haven't reported it "upstream" either.

So it looks like ndiswrapper being sucky. Will you get a chance to test this or should I just close this bug as unresolved?