Re: usb-Atmel - Ad0-Hoc - ZyAIR B-200 - Wifi Link OK, TCP/IP Link dead
Joerg Albert <[email protected]>
| Newsgroups | gmane.linux.drivers.atmel-wlan |
|---|---|
| Message-ID | <Pine.LNX.4.56.0307121340180.530@invb> |
Hi Jörg, On Sat, 12 Jul 2003, Joerg Mertin wrote: > From my Networking Background - what I see is that the Sun-System has a > weird setup. The iwconfig output gives me the mac address of the remote > device - however the ifconfig shows the Mac address of the Local device. > Seems like a proxy-Arping to me - but how am I supposed to configure a > routing table into that ? iwconfig never displays the local MAC address under "Cell:". It shows either the IBSS id choosen if it has started its own IBSS in ad-hoc mode or the (I)BSS id joined if (a) in managed mode or (b) if it had joined an already existing IBSS (i.e. if it was not the first STA started for a given SSID in mode ad-hoc). > Note - that I can run the Prism3 based Wifi under Windows XP - and there > is no difference in beheaviour at all - so I really think the problem is > on the atmel-device side. Not necessarily. Old Prism2 firmware (you didn't post which one you use) seems to have problems in ad-hoc mode - grep the lwlan-ng mailing lists. I had a Prism2 PCMCIA card with 0.8.3 inside which (if it started the IBSS first) sometimes decided to leave the IBSS by itself. Windows driver might load newer fw versions into RAM on startup. Try starting both devices in a different order (AFAIR starting the Atmel-USB first fixed my problem with the 0.8.3 Prism firmware - but I used the Berlios driver). I'm of little help with the Sourceforge USB driver. If you could get another Prism2/2.5/3 device you may use it in monitor mode to trace the air traffic. /Jörg