Curious. Absolutely nothing worked for me with the lynksys ae1000 and any of the 3.0.x kernels.
Did you configure support in the kernel and compile it or did you use precompiled modules from debian?[/quote3dn12wgx]
there is only one driver that i have been able to use and it comes with a kernel you have to compile it all
i guess they modifed a kernel module
the kernel is not to old..2.6.33 i believe
and guess what
the driver is flawless
so i know they can do it because im living proof
i turned my RT3572 into an AP/MASTER the other night with airbase-ng
it dropped quite a bit and slow speeds (but everyone was getting that with their other AP devices so that was normal)
i am now messing with hostapd as i think it will be alot faster
i have gotten it to show up as an AP but my routing or something is off because when i connect i cant get anything past the lan.
i know its just me configuring stuff and soon it will work
i made a couple guides...i should say i RE-DID a couple guides to get it to work (the rt2x00 driver or rt2800usb w/e it is.
works for SURE 100% as of one week ago unless someone has changed something
anyhow the "git" that gets the kernel and the modified driver why dont someone do a 'diff' on a default kernel and the kernel that is from git or from the git checkout and maybe we can package the source so we can include it with newer kernels?
someone that knows more then me should be able to do this easily.
anyhow if you have any Q`s let me know because mine is working perfect...i just dont like not being able to leave kernel 2.6.33 because if i do my rt3572 wont work anymore from what i read
i mean it works in monitor mode, packet injection, AP/Master mode....it works with everything i can throw at is...im just stuck with kernel 2.6.33 because no matter what rt2x00 says about it supporting the rt3572 chipset....i was never able to get it to do anything besides the regular ralink STA drivers (which means it cant do anything but be a client and adhoc)
to my understanding
if someone that knows the rt2x00 (compat-wireless) well and they know the RT3572 chipset well can you please verify what it can do besides be a client and adhoc?