This is a reply to Marc which may be interresting to the list as well.
(His original mail is left out)
I have this Zydas based USB stick (which seems a bit weird to configure) and a
Ralink based PCI card (that has an extremely buggy driver).
Since I don't fully trust either, I tried to verify softAP once more.
On the Zydas based host I ran driver version 2_2_0_0 from the Zydas web site.
I only use iwconfig to set it up like I described in my earlier post.
On the Ralink based client I saw a message in the log indicating it detected
the Zydas host as an AP:
Oct 25 08:59:21 vp6 kernel: *RT25*<7>SYNC - New AP added to SsidBssTab,
(I XX-ed out the MAC address, but I can assure you that it matches the MAC of
the Zydas USB stick)
Unfortunately I wasn't able to connect the client to the host in managed mode
as the client crashed my computer on every connection attempt. (This is
possibly related to the Ralink driver not being happy with a 4kstacks kernel)
I can also confirm that the Zydas host sends out numerous beacons that
identify it as an AP. (I verified this by sniffing the packets and viewing
them in ethereal)
Decided to take a different approach:
Borrowed my parents Windows XP machine to use as a client.
It recognised and connected to the Zydas softAP without a hitch.
The log on the Zydas host showed a STA_ASSOCIATED message for the client's
MAC. The client's network properties showed it was associated to the real MAC
address of the Zydas softAP, indicating an infrastructure network ???, not
some phony, random BSSID like in ad-hoc mode.
I used an open AP, so no encryption. Both machines could ping each other.
I didn't do, or haven't got the intention to do any further testing right now.
Looking at the log you posted I noticed a thing or two that differ from me:
- You're connected to a USB 1.1 host (USB 2.0 for me), but apart from reduced
speeds I don't see an apparent problem with that.
- your firmware version indicates 4810 while your EEPROM version indicates
4330. I'm not sure if that makes a difference. What I understand from reading
the code (a while back) is that the firmware version is the revision of your
hardware, the EEPROM version is the revision of the additional code that gets
uploaded to the hardware when the USB stick is plugged in.
I have 4330 for both so my stick is probably an older revision than yours but
at least the two revisions match.
- your driver version is 2_0_0_0, maybe the 2_2_0_0 driver is a better match
to your firmware.
- I do not suffer from the kobject error.
- I use the driver from the Zydas web site.
Get latest updates about Open Source Projects, Conferences and News.