The following reply was made to PR kern/132722; it has been noted by GNATS.
From: Matthias Apitz <g...@unixarea.de>
To: Sam Leffler <s...@freebsd.org>
Cc: bug-follo...@freebsd.org, freebsd-net@freebsd.org
Subject: Re: kern/132722: [ath] Wifi ath0 associates fine with AP, but DHCP or
IP does not work
Date: Mon, 23 Mar 2009 22:42:07 +0100
El día Monday, March 23, 2009 a las 12:12:04PM -0700, Sam Leffler escribió:
> If you have the raw pcap capture please provide a url to it.
I have to capture it and will provide it;
>
> From the log it appears you're sending+receiving wep-encrypted frames.
> They keyid is the same and since you're receiving frames I have to
> assume the key matter is correct as otherwise the h/w would drop the
> frame. You can verify this by feeding the key into wireshark to check
> if the frame contents make sense.
>
> I'm out of ideas. About the only thing I can suggest is you setup a
> different ap w/ the same wep key and see if things work. If so then you
> know it's something this ap is doing. I can't recall when I last tested
> wep on HEAD but I'm pretty sure it works. I will re-test that when I
> get a chance.
>
> Sam
WEP in general works; my AP at home is configured as WEP and the entries
in wpa_supplicant.conf are nearly the same, only the key differs:
# my home
#
network={
ssid="tarara"
scan_ssid=0
key_mgmt=NONE
wep_tx_keyidx=0
wep_key0=xxxxxxxxxx
}
# Restaurante Odyssee (2007-11-18)
#
network={
ssid="ConnectionPoint"
scan_ssid=0
key_mgmt=NONE
wep_tx_keyidx=0
wep_key0=xxxxxxxxxxxxxxxxxxxx
}
but I will configure another AP to also use the same wep_key0, if you
think that the problem could depend on the key itself;
and I will check if I could get somewhere this model of AP for a test;
matthias
_______________________________________________
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
