wpasupplicant in dapper doesn't work with madwifi-ng
Bug #47144 reported by
Allison Karlitskaya
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Dapper Backports |
Invalid
|
Low
|
Unassigned | ||
wpasupplicant (Ubuntu) |
Fix Released
|
Medium
|
Reinhard Tartler | ||
Dapper |
Won't Fix
|
Medium
|
Unassigned |
Bug Description
the wpasupplicant in dapper is built against old madwifi headers. this prevents it from working with madwifi-ng.
this is a bit of a contradiction considering that in a fresh dapper install the madwifi-ng (not the madwifi) drivers get loaded by default on my laptop.
there is a comment in the patch that installs the madwifi headers into the wpasupplicant build tree that this patch prevents wpasupplicant from working with madwifi-ng. i fixed this problem for myself by building with the new headers (i also used a newer version of wpasupplicant).
things are working great now, but it'd be nice if i didn't have to build my own wpasupplicant.
Changed in wpasupplicant (Ubuntu Dapper): | |
status: | Confirmed → Won't Fix |
To post a comment you must log in.
please use -Wext on madwifi-ng. I have been told that madwifi-ng would implement all required wireless extensions, so this should do.
Does this work for you?