Re: usb-Atmel - Ad0-Hoc - ZyAIR B-200 - Wifi Link OK, TCP/IP Link dead

Hi Joerg,

thx for the Hint. It's a prism3 card actually - from the following data:
usb.c: registered new driver prism2_usb
ident: nic h/w: id=0x8026 1.0.0
ident: pri f/w: id=0x15 1.1.0
ident: sta f/w: id=0x1f 1.4.2

The 0x8026 Identifies it as a prism 3 chip.
The Firmware version - I dojn't know which entry I have to use from head.
1.1.0 or 1.4.2 ? Well - so it's a fairly new card.

Regarding the IBSS - I figured it out. However - what I never saw anywhere
mentioned - is how do the BSSI need to be set for the Add-Hoc mode to
work, and how do the Mac-Addresses on the ofconfig call work.

So - does the CELL-Entry has to look the same on both sides ? Or, in case
of a WiFi Link, do the devices exchange their IBSS's ?
How about the Mac-Addresses of the "Virtual" network devices ? Are these
also communicated to the remote side or not ?

Could anyone here having a Working Add-Hoc config provide me the iwconfig
and ifconfig output of their 2 Endpoints ? This would help me a lot.

It's always hard to dig into something - when you don't know what it
should look like :)

Joerg Albert said:
> 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).

So - If I understood correctly - in case B here, Pandora had it's IBSS:
02:A0:70:C0:63:CE - and when I tell my Atmel based device to connect it,
this one will copy the IBSS from Pandora to the Sun System, showing me the
same IBSS in the Cell line ...
So far - so good. got that one.

>> 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).

Ohf - you're talking to an Old LInux guy here :) That was the third thing
I tried out ;)
BTW - does the Berlios Driver support the iwconfig from the wireless tools
???
The linux-wlan-ng has an own set of tools - and I do admit I do prefere
using the wireless-tools API. It's coping better into the ifconfig logic
:)


> 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.

Actually - I do have a ZyAir B100 hanging around here. The Problem is that
I have only a very  old subnotebook with a 486DX2-50MHz System - and a
very old Linux Redhat-6.1 Distribution runing on it. Maybe I'll give it a
try to compile the drivers etc.

Thanx & Cheers

	Joerg
-- 
------------------------------------------------------------------------
| Joerg Mertin              :  [email protected]                (Home)|
| in Neuchâtel/Schweiz      :                                          |
| Stardust's LiNUX System   :                                          |
| PGP 2.6.3in Key on Demand :  Voice & Fax: +41(0)32 / 725 52 54       |
------------------------------------------------------------------------
Home-Page: http://www.solsys.org