Hi Folks

I made considerable progress in my attempt to get the wifi client up and
running.
I found a simple network definition for wpasupplicant which would
sufficiently describe the connection to my WRT54GH

STYX# cat /etc/wpa_supplicant.conf
ctrl_interface=/var/run/wpa_supplicant
update_config=1

network={
        ssid="scoobly"
        psk="xxxxxxxxxxx"
}

and here is the status

STYX# wpa_cli status
Selected interface 'wlan0'
bssid=00:25:9c:09:aa:12
ssid=scoobly
id=0
pairwise_cipher=CCMP
group_cipher=TKIP
key_mgmt=WPA2-PSK
wpa_state=COMPLETED
ip_address=192.168.217.100

The IP address is obtained using dhcp, so I assume the most basic
connectivity is there.

When I try top ping the AP then all I see on the interface is arp requests

STYX# tcpdump -i wlan0
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on wlan0, link-type EN10MB (Ethernet), capture size 65535 bytes
20:17:07.791504 ARP, Request who-has 192.168.217.1 tell 192.168.217.100,
length 28
20:17:08.793505 ARP, Request who-has 192.168.217.1 tell 192.168.217.100,
length 28
20:17:10.793533 ARP, Request who-has 192.168.217.1 tell 192.168.217.100,
length 28
20:17:11.795505 ARP, Request who-has 192.168.217.1 tell 192.168.217.100,
length 28
^C
4 packets captured
4 packets received by filter
0 packets dropped by kernel

So it appears that packets are passed at a certain moment.

If I disconnect and reassociate the following can be seen

STYX# tcpdump -i wlan0
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on wlan0, link-type EN10MB (Ethernet), capture size 65535 bytes
20:19:13.339501 ARP, Request who-has 192.168.217.1 tell 192.168.217.100,
length 28
20:19:36.559619 EAPOL key (3) v1, len 117
20:19:36.562865 EAPOL key (3) v1, len 117
20:19:36.576570 EAPOL key (3) v1, len 175
20:19:36.579198 EAPOL key (3) v1, len 95
20:19:36.666855 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP,
Request from 00:0b:6b:36:bb:cd (oui Unknown), length 321
20:19:37.770728 IP 192.168.217.1.bootps > 255.255.255.255.bootpc:
BOOTP/DHCP, Reply, length 300
20:19:37.777122 ARP, Request who-has 192.168.217.100 tell 0.0.0.0, length 28

It appears that the connection comes up fine and dhcp takes place. Still
I cannot reach the AP.

When I enter the arp address manually I can see ICMP echos leaving
through wlan0, but no reply. It feels like the AP does not want to talk
to me.

Using my windoze laptop with the same AP I can ping without a problem :-(

Any ideas?

Thanks

Erich

Attachment: smime.p7s
Description: S/MIME Kryptografische Unterschrift

------------------------------------------------------------------------------
Doing More with Less: The Next Generation Virtual Desktop 
What are the key obstacles that have prevented many mid-market businesses
from deploying virtual desktops?   How do next-generation virtual desktops
provide companies an easier-to-deploy, easier-to-manage and more affordable
virtual desktop model.http://www.accelacomm.com/jaw/sfnl/114/51426474/
------------------------------------------------------------------------
leaf-user mailing list: leaf-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/leaf-user
Support Request -- http://leaf-project.org/

Reply via email to