Sitecom Walklan aka Bluetake BW002

Odo Maletzki <[email protected]> Tue, 28 Oct 2003 02:29:24 +0100
Newsgroups gmane.linux.drivers.atmel-wlan
Message-ID <5160000.1067304564@[10.10.10.10]>
Hello,

I just bought a Sitecom WLAN-Set. It is frustrating...
The PCMCIA-Card in the package is a WL-011v2, not the WL-011 which means: 
no linux support yet (AMD 1772)
and the USB-WLAN-Adapter, which is actually a Bluetake BW002 with a 
sitecom-label doesnt connect to the access-point. WIth windows everything 
works fine.

Maybe somebody can help with the connection of the USB-Adapter:


I have Debian, Kernel 2.4.22
I use at76c503.10-drivers for my USB-Device


1) iwconfig is fine
2) ifconfig is fine
3) arp -n shows "inclompete" for the MAC-Adress of the access-point
4) route -n is fine
5) ping doesn't work

why?


Here is my "lsmod" (excerpt)

--->
Module                  Size  Used by    Not tainted
.
.
.
at76c503-rfmd          39456   0
at76c503               55456   0  [at76c503-rfmd]
usbdfu                  8044   0  [at76c503-rfmd]
uhci                   25916   0  (unused)
usbcore                63308   1  [at76c503-rfmd at76c503 usbdfu hid uhci]
.
.
.
<---

"at76c503" was started with debug-option



Here is my /etc/network/interfaces (excerpt)


--->
auto wlan0
iface wlan0 inet static
        address 192.168.1.133
        netmask 255.255.255.0
        network 192.168.1.0
        broadcast 192.168.1.255
        gateway 192.168.1.1
<---


The access-point-config is web-based. Here is all I can do for WLAN

--->
LAN-IP: 192.168.1.1
netmask: 255.55.255.0
ESSID : maletzki	
Channel : 1	
WEP : Disabled
Access Permission : 	Allow Everyone Access
<---


When I plug the USB-Device to my notebook, syslog says:


Oct 28 01:04:55 moon44 kernel: hub.c: new USB device 00:07.2-1, assigned 
address 5
Oct 28 01:04:55 moon44 kernel: usbdfu.c: Downloading firmware for USB 
device 5...
Oct 28 01:04:57 moon44 kernel: at76c503.c: $Id: at76c503.c,v 1.35 
2003/07/30 06:31:51 jal2 Exp $ compiled Oct 28 2003 00:17:20
Oct 28 01:04:57 moon44 kernel: at76c503.c: firmware version 1.101.2 #84 
(fcs_len 4)
Oct 28 01:04:57 moon44 kernel: at76c503.c: device's MAC 00:30:00:11:37:cc, 
regulatory domain <unknown> (id 255)
Oct 28 01:04:57 moon44 kernel: at76c503.c: registered wlan0


Then, i do

># iwconfig wlan0 channel 1 essid "maletzki"
># ifconfig wlan0 up

the result:

syslog says:


Oct 28 01:06:19 moon44 kernel: at76c503.c: wlan0 param: ssid maletzki 
(6D616C65747A6B69) mode adhoc ch 1 wep disabled key 0 keylen 0
Oct 28 01:06:19 moon44 kernel: at76c503.c: wlan0 param: preamble long rts 
1536 frag 1536 txrate auto excl 0
Oct 28 01:06:19 moon44 kernel: at76c503.c: wlan0 param: pm_mode 1 pm_period 
0 auth_mode open scan_times 10 120 scan_mode active
Oct 28 01:06:20 moon44 kernel: at76c503.c: wlan0: state 0 -> 1 (SCANNING)
Oct 28 01:06:20 moon44 kernel: at76c503.c: wlan0 BSS table (curr=00000000, 
new=00000000):
Oct 28 01:06:20 moon44 kernel: at76c503.c: 0xca1b6bc0: bssid 
00:03:6d:f2:ed:64 channel 1 ssid maletzki (6D616C65747A6B69) capa x0001 
rates 82 84 0B 16 rssi 37 link 0 noise 0
Oct 28 01:06:21 moon44 kernel: at76c503.c: wlan0 BSS table (curr=00000000, 
new=00000000):
Oct 28 01:06:21 moon44 kernel: at76c503.c: 0xca1b6bc0: bssid 
00:03:6d:f2:ed:64 channel 1 ssid maletzki (6D616C65747A6B69) capa x0001 
rates 82 84 0B 16 rssi 36 link 0 noise 0
Oct 28 01:06:21 moon44 kernel: at76c503.c: wlan0: state 1 -> 6 (JOINING)
Oct 28 01:06:21 moon44 kernel: at76c503.c: wlan0 find_matching_bss: 
returned 00000000
Oct 28 01:06:21 moon44 kernel: at76c503.c: wlan0: state 6 -> 8 (STARTIBSS)
Oct 28 01:06:21 moon44 kernel: at76c503.c: using BSSID 02:00:bf:ec:18:00

Oct 28 01:08:01 moon44 kernel: at76c503.c: wlan0 tx  wlen x4e pad x1c rate 
4 hdr 08000000FFFFFFFFFFFF0030001137CC0200BFEC18000000
Oct 28 01:08:18 moon44 last message repeated 11 times



># iwconfig

lo        no wireless extensions.

eth0      no wireless extensions.

wlan0     IEEE 802.11-DS  ESSID:"essidtest"  Nickname:"okuwlan"
          Mode:Ad-Hoc  Channel:1  Cell: 02:00:6C:FA:7E:0D
          Bit Rate:11Mb/s
          RTS thr=1536 B   Fragment thr=1536 B
          Encryption key:off
          Power Management:off
          Link Quality:0  Signal level:80  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


># ifconfig

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:241 errors:0 dropped:0 overruns:0 frame:0
          TX packets:241 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:21824 (21.3 KiB)  TX bytes:21824 (21.3 KiB)

wlan0     Link encap:Ethernet  HWaddr 00:30:00:11:37:CC
          inet addr:192.168.1.133  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          RX bytes:0 (0.0 b)  TX bytes:720 (720.0 b)




># arp -n

Address     HWtype  HWaddress           Flags Mask            Iface
192.168.1.1         (incomplete)                              wlan0


># route -n

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use 
Iface
192.168.1.0     0.0.0.0         255.255.255.0   U     0      0        0 
wlan0
0.0.0.0         192.168.1.1     0.0.0.0         UG    0      0        0 
wlan0


># arping -i wlan0 192.168.1.1
ARPING 192.168.1.1


...and nothing happens, except these messages in the syslog:

Oct 28 01:09:46 moon44 last message repeated 3 times
Oct 28 01:10:15 moon44 last message repeated 12 times




What is my problem?
For me it looks like the USB-device works fine but doesn't find the 
access-point.

BTW:

1) with the atmelwlandriver-ss-20030923 - tarball-drivers the device is not 
recognized.
2) when I use usb-uhci instead of uhci the atmewlandrivers crash my system 
(and another one as well. So it is a problem of debian o the drivers)
3) With the at76c503-drivers I can use either uhci or usb-uhci

4) "route -n" is ok but "route" is slow (1st line immediately, 2nd line 
after 10 secs.)
5) "arp -n" is ok  but "arp" has a delay of 10 secs



PLEASE HELP


Greetings
Odo
[email protected]