OESF Portables Forum
Everything Else => General Support and Discussion => Zaurus General Forums => Archived Forums => Security and Networking => Topic started by: alge on December 16, 2004, 06:11:47 pm
-
Hi,
I just got my new SL 6000L and I'm trying to connect to my WRT54G access point
(SHARP ROM version 1.12)
I'm sure that I got all setup entries right, because I can use the same setup successfully (ESSID, WEP keys) when I plug my SMC 2642W CF card in (which I normally use in my SL-5000D). MAC address filtering is turned of at the AP.
I even tried to disable WEP on the WRT54G but I could not connect at all.
When I look at ifconfig ouput during the connection trial, I see only 3 or 4 dropped packets in the TX/RX statistics.
After the connection trial (tapping the network icon in status bar) the wlan0 device is removed, can anybody tell me how to start the connection manually from a terminal? It would help debugging my setup a lot.
I already tried
/etc/wlan/wlan-setup start wlan0 qpewlan0which is running after the click on the network icon, but this seems only to be the second part of scripts which have to be run, it already expects a wlan0 device to be present. How can I create this manually, reloading prism2_usb module is not enough. I guess some hotplug script has to be run, but which one?
I tried also at work with some Cisco access point (forgot model name), also no connection there.
By enabling lots of debug options we could at least see some packets which came from the hardware address of the SL6000.
Below is my dmesg output of a connection attempt, I'm a bit unsure if the hex-0 serial number is ok, because with my WDC card I can see some integer there, could anybody look at his dmesg output if it looks similar?
ub.c: USB new device connect on bus1/2, assigned device number 2
usb.c: USB device 2 (vend/prod 0xbb2/0x302) is not claimed by any active driver.
init_module: prism2_usb.o: 0.2.0 Loaded
init_module: dev_info is: prism2_usb
usb.c: registered new driver prism2_usb
ident: nic h/w: id=0x8026 1.0.0
ident: pri f/w: id=0x15 1.1.3
ident: sta f/w: id=0x1f 1.7.4
MFI:SUP:role=0x00:id=0x01:var=0x01:b/t=1/1
CFI:SUP:role=0x00:id=0x02:var=0x02:b/t=1/1
PRI:SUP:role=0x00:id=0x03:var=0x01:b/t=1/4
STA:SUP:role=0x00:id=0x04:var=0x01:b/t=1/12
PRI-CFI:ACT:role=0x01:id=0x02:var=0x02:b/t=1/1
STA-CFI:ACT:role=0x01:id=0x02:var=0x02:b/t=1/1
STA-MFI:ACT:role=0x01:id=0x01:var=0x01:b/t=1/1
Prism2 card SN: \x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00
p80211knetdev_hard_start_xmit: Tx attempt prior to association, frame dropped.
p80211knetdev_hard_start_xmit: Tx attempt prior to association, frame dropped.
p80211knetdev_hard_start_xmit: Tx attempt prior to association, frame dropped.
usb.c: USB disconnect on device 2
thanks
-
I'm afraid I can't help much. I can tell you that I've connect to my friends wireless rounter with my 5600. And I'm pretty sure he had a WRT54G.
-
Not to ask a stupid question but are you sure the MAC filter is turned off? Are you assigning IP addrs based upon MAC id? I messed around for about two hours until I remembered that I had to tweak these (but I'm using a different AP).
There was a post earlier (months?) about the four WEP fields needing to be setup with the WEP key value. I did not need to do that for my AP but it might be worth a try.
-
slapout: maybe the problem is that I don't use the original firmware on the WRT54G but a modified version from sveasoft.com. And I also enabled WDS between my two access points (both running in mixed 11/54 Mbit mode).
I'll soon get another WRT54G and will try with original firmware.
Meanwhile I found a public hotsot near university where I could connect to the login portal immediately, so now I'm sure that my SL6000's wifi card is not damaged at least.
Tehas: Yes i forgot about this in my first try , but i already had disabled HWA matching before.
Maybe I'should try enabling it and put the new HWA in the accepted HWA list...
I also tested the WLAN parameters (WEP ...) by using the same setup with my SMC CF card and it works there.
The problem with the internal USB Prism2 even occurs before any DHCP packets have to be send, this can only happen after you are authenticated and associated to the accesspoint (that means you can see the APs harware adress listed when you call iwconfig wlan0).
Meanwile i also tried a Cisco AP (Airo-AP1231) with the same result. The log output on this AP shows my HWA with th error code: Auth_not_Assoc
I'll kkep trying, I guess I have to create a systematic experimental plan with enabling/disabling several AP features (mixed mode, WDS bridging or not and so on)
Meanwhile I also learned some of the wlanctl-ng subcommands. in any case I can scan successfully for APs with "wlanctl-ng dot11req_scan ...." and "wlanctl-ng dot11req_scan_results ...." which shows me the SSID and BSSID (HWA) of the AP.
I compared these results with results from the SMC CF card and they only differ in the ibssatimwindow parameter (=0 for working SMC card, =65105 for SL6000 internal card). I still don't know what this means and if it has any meaning to my problem.
Thanks
Albrecht
-
just for completeness: I also figured out (using this forum) how to start the internal wlan device manually
usbctl on 1
sleep 2
wlanctl-ng wlan0 lnxreq_ifstate ifstate=enable
A scan for an AP can be done by
wlanctl-ng wlan0 dot11req_scan bsstype=any bssid=ff:ff:ff:ff:ff:ff ssid="" \
scantype=both channellist="00:01:02:03:04:05:06:07:08:09:0a:0b:00:00" \
minchanneltime=200 maxchanneltime=250
and if the return value contains a "numbss" value >=1 you can get the scan results by
wlanctl-ng wlan0 dot11req_scan_results bssindex=0where you can iterate bssindex from 0 to numbss-1.
-
slapout: maybe the problem is that I don't use the original firmware on the WRT54G but a modified version from sveasoft.com. And I also enabled WDS between my two access points (both running in mixed 11/54 Mbit mode).
Albrecht,
I am using a wrt54g with software from sveasoft. I am _not_ running WDS, however. Mine connects just fine.
Is there a reason why you aren't using the built in GUI (the little world icon) to connect? It is what I use, and it works for me.
I hope this helps,
Craig...
-
I also tried connecting via GUI, but when this fails, you have not many debugging options, thats why I used these manual wlan startup commands.
Currently I'm using a third WRT54GS with original firmware (there is no connection problem) behind my WDS bridge for the 6000L.
I thought that I also tried sveasoft firmware without WDS, but I have to repeat those tests to be sure.
Albrecht
-
I also tried connecting via GUI, but when this fails, you have not many debugging options, thats why I used these manual wlan startup commands.
Currently I'm using a third WRT54GS with original firmware (there is no connection problem) behind my WDS bridge for the 6000L.
I thought that I also tried sveasoft firmware without WDS, but I have to repeat those tests to be sure.
Albrecht
Albrecht,
Perhaps a network diagram would help. Does you network look like this?
Internet--->Firewall---->wrt54gs------WDS----->wrt54gs----->Zaurus SL6000
I am trying to understand you network better. I now have 2 wrt54g's so I can test the WDS setup (although I am running SveaSoft 4.x) if you like.
Craig...
-
this didn't work:
Internet--->Firewall==wrt54g/svea------WDS----->wrt54g/svea----->Zaurus SL6000
after changing to
Internet--->Firewall==wrt54g/svea------WDS----->wrt54g/svea--cable->wrt54gs/linksys/otherESSID--->Zaurus SL6000
it worked.
but meanwhile I recognized that it wasn't related to the firmware, it also stopped working with linksys firmware on the last wrt54gs after changing channels.
It turned out it only works for me with channel 10, 11 or 12. before I recognized this I had channel=auto (it switched to 1 or 2), this didn't work.
I think it's related to my neighbour networks (on 801.11g on channel 6), maybe the antenna in the Z is not as good as that one in my SMC card.
It can also be partly related to WDS: now I'm back at a two wrt54 setup with sveasoft and WDS. sometimes it doesn't connect, maybe because both APs with same ESSID are visible? But if I execute before tapping the connect icon:
usbctl on 1
sleep 2
wlanctl-ng wlan0 lnxreq_ifstate ifstate=enable
wlanctl-ng wlan0 dot11req_scan bsstype=any bssid=ff:ff:ff:ff:ff:ff ssid="" \
scantype=both channellist="00:01:02:03:04:05:06:07:08:09:0a:0b:00:00" \
minchanneltime=200 maxchanneltime=250
it works. I'll have a look for the wlan scripts where I can add this permanently...
Albrecht