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

Joerg Mertin <[email protected]>
Newsgroups gmane.linux.drivers.atmel-wlan
Message-ID <[email protected]>
Hi again Joerg,

thx for the clarification. However - have you seen this strange behaviour 
somewhere before ?

wlan0 (WE) : Buffer for request 8B1B too small (0<14)
wlan0 (WE) : Buffer for request 8B1B too small (0<14)
wlan0 (WE) : Buffer for request 8B1B too small (0<14)

The only reference I found in google has it's Mailbox deactivated due to 
inactivity...

On Tuesday 15 July 2003 22:15, Joerg Albert wrote:
> Hi Joerg,
>
> just saw your second posting - you've got it working, kind of.
>
> Some remarks left:
> > > What are "virtual" network devices?
> >
> > OK - Virtual Network Devices. I call always Virtual Network Device a
> > device that is used to attach an existing network Device on the computer.
> > In this case - the wlan-devices you see through iwconfig are the real
> > ones - while the wlan-device you see through ifconfig is the virtual one
> > - virtually attached to the wireless device in my point of view :)
> > (e.g. I have worked with so many Intranet based stuff that I start
> > developing my own vocabulary. b.e. if you use a /32 Network to connect 2
> > sites together, I call this Network the "Transit" subnet etc.)... be
> > gentle ;) I might become too old for this stuff *lol*
>
> IMHO they are "real" network devices - they've simply got a physical
> layer different to wired Ethernet. Different collision avoidance,
> packaging etc., but they still are 802.xx devices.

Yes - they are - but they are on a different phisical layer as you said :)

> > Is there something like a packet-Sniffer that tells me what is going on
> > on the W-Lan - Wireless part ?
>
> yes. I use a Prism2 PCMCIA card with wlan-ng in monitor mode for testing
> (Prism2 USB devices should work as well) and ethereal >= 0.9.9 .
> Just call
> 	./sniff.sh wlan0 12
> 	ifconfig wlan0 up
> 	ethereal -i wlan0
> with sniff.sh as
>
> #!/bin/bash
> # file: sniff.sh
> echo "setting dev $1 to sniff on channel $2"
> wlanctl-ng $1 lnxreq_wlansniff enable=true channel=$2 \
>   prismheader=true wlanheader=true keepwepflags=true stripfcs=false
>
> This will show you all WLAN traffic on channel 12.

Yeah - between te time I wrote my Mail and you wrote yours - I found that tool 
too :) Downloaded it - but not using it yet ;)

> The only problem here is to decrypt WEP in the trace (I'm using ancient
> sta fw 0.8.3 which needs WEP support in the driver).

I'll check it out. Thx for the Hint.

Cheers

	Joerg M.
-- 
The only reward of virtue is virtue.
		-- Ralph Waldo Emerson
------------------------------------------------------------------------
| Joerg Mertin              :  [email protected]                (Home)|
| in Neuchâtel/Schweiz      :  [email protected]                  (Alt1)|
| Stardust's LiNUX System   :  [email protected]                (Alt2)|
| PGP 2.6.3in Key on Demand :  Voice & Fax: +41(0)32 / 725 52 54       |
------------------------------------------------------------------------
Home-Page: http://www.solsys.org
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.