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

Hi Joerg :)

sorry for the late answer - but I had some things that came in the way.

On Saturday 12 July 2003 19:22, Joerg Albert wrote:
> Hi Jörg,
>
> On Sat, 12 Jul 2003, Joerg Mertin wrote:
> > 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
>
> I was talking about the station fw - your 1.4.2 is fairly new.
The station firmWare - if I understood it correctly - is an Atmel-Based 
System, RFMD503A, Driver Version : 2.1.2.2, Firmware Version : 1.101.2.84
Using the lvnet - I can even put it into Access-Point mode. So at least - that 
should be ok :) However - when enabing it - I'm still not able to connect to 
it using a prism3 based device. I bet something really ugly is happenning 
somewhere - but I don't get it ...

[...]

> For ad-hoc mode, the "Cell:" entries must show the same addr. Be aware
> that wlan-ng does not fully support the wireless extensions, i.e. using
> iwconfig to obtain information may be broken. In my case iwconfig did not
> show the correct "Cell:" id, I had to use their own tools
> (wlanctl-ng/wlancfg ?).
>
> In ad-hoc mode the first STA started usually scans for the given SSID and
> if it cannot find a IBSS with it, starts its own, choosing a random BSSID
> and using the configure channel. The second STA scans as well and find
> this IBSS. If this fails for any reason, it starts a second IBSS and no
> communication is possible.
>
> > How about the Mac-Addresses of the "Virtual" network devices ? Are these
> > also communicated to the remote side or not ?
>
> 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*

> no, sorry, have no running ad-hoc config here. But IMHO your setup looks
> OK. I would:
Yeah - what I think too:
Sun:
eth3      ATMEL RFMD503A  ESSID:"SolSys_pandora"  Nickname:"SolSys_pandora"
          Mode:Ad-Hoc  Channel:4  Cell: 02:A0:F9:39:63:CE
          Bit Rate:2Gb/s
          RTS thr=2347 B   Fragment thr=2346 B
          Encryption key:off
          Link Quality:100  Signal level:12  Noise level:0
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

eth3      Link encap:Ethernet  HWaddr 00:06:F4:03:06:FF
          inet addr:10.0.4.1  Bcast:10.0.4.7  Mask:255.255.255.248
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:44 errors:1 dropped:0 overruns:0 frame:0
          TX packets:1113 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          RX bytes:1932 (1.8 Kb)  TX bytes:102350 (99.9 Kb)

Arp table:
pandora.solsys.org (10.0.2.47) at 00:40:63:CB:60:1C [ether] on eth0
? (10.0.4.3) at <incomplete> on eth3

However - some packets seem to get through - or they might just be the deny 
packets ?

Pandora:
wlan0     IEEE 802.11-b  ESSID:"SolSys_pandora"  Nickname:"SolSys_pandora"
          Mode:Ad-Hoc  Frequency:2.427GHz  Cell: 02:A0:F9:39:63:CE
          Bit Rate:2Mb/s   Tx-Power:2346 dBm
          Retry min limit:8   RTS thr:off   Fragment thr:off
          Encryption key:off
          Link Quality:92/92  Signal level:-40 dBm  Noise level:-93 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

wlan0     Link encap:Ethernet  HWaddr 00:A0:C5:41:63:CE
          inet addr:10.0.4.3  Bcast:10.0.4.7  Mask:255.255.255.248
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1 errors:0 dropped:0 overruns:0 frame:0
          TX packets:408 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0
          RX bytes:84 (84.0 b)  TX bytes:14856 (14.5 Kb)

Arp table:
[root@pandora wlan]# arp -a
sun.solsys.org (10.0.2.1) at 00:40:F4:67:45:E4 [ether] on eth0
? (10.0.4.1) at <incomplete> on wlan0


> - compare the Prism2's iwconfig output to the wlan tools' output
I tried - but can't come behind the logic used in the package. Just installed 
the latest one and still - no go. 
[root@pandora wlan]# ping 10.0.4.1
PING 10.0.4.1 (10.0.4.1) 56(84) bytes of data.
From 10.0.4.3 icmp_seq=1 Destination Host Unreachable
From 10.0.4.3 icmp_seq=2 Destination Host Unreachable
From 10.0.4.3 icmp_seq=3 Destination Host Unreachable

For the tcpdump - while doing a ping - I get on both sides:
tcpdump: listening on eth3
17:12:15.473217 arp who-has 10.0.4.3 tell 10.0.4.1
17:12:16.470035 arp who-has 10.0.4.3 tell 10.0.4.1
17:12:17.470029 arp who-has 10.0.4.3 tell 10.0.4.1
17:12:44.450883 10.0.4.1.who > 10.0.4.7.who: udp 132 (DF)

and:
tcpdump: listening on wlan0
17:13:01.204727 arp who-has 10.0.4.1 tell 10.0.4.3
17:13:02.195995 arp who-has 10.0.4.1 tell 10.0.4.3
17:13:03.195996 arp who-has 10.0.4.1 tell 10.0.4.3
17:13:15.203697 10.0.4.3.who > 10.0.4.7.who: udp 84 (DF)

Don't know about the 2 last... Note that I'm not filtering anything out.
The Broadcast-Ping does not give anything back...

Is there something like a packet-Sniffer that tells me what is going on on the 
W-Lan - Wireless part ?

BTW - From time to time I get on Sun:
17:19:27.347721 arp who-has 10.0.4.1 tell 10.0.4.3
17:19:27.347797 arp reply 10.0.4.1 is-at 0:6:f4:3:6:ff
17:19:28.344550 arp who-has 10.0.4.1 tell 10.0.4.3
17:19:28.344605 arp reply 10.0.4.1 is-at 0:6:f4:3:6:ff

and then an Entry in the arp-table:
? (10.0.4.3) at 00:A0:C5:41:63:CE [ether] on eth3

this does not work on Pandora however ...

Any more hints ???
PS: I also tried the berlios drivers - they didn't make a difference ...

I bet - it's such a tiny thing that I'm missing - but what ???


Thx in advance for your time & Cheers

	Joerg M.

> - try different start order
> - run tcpdump in the background in case some data got corrupted
> - check if ARP entries are received for the peer
> - try broadcast pings
>
> /Jörg
-- 
Trying to be happy is like trying to build a machine for which the only
specification is that it should run noiselessly.
------------------------------------------------------------------------
| 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