slhac tivist <[email protected]> writes:
> I can get athn0 to "link", but then it sends a dozen DHCPREQUESTs, and then
> sends DHCPDISCOVERs until it sleeps...
>
> I've never had this problem before. Last time I switch routers, I just
> changed nwid, and wpakey with ifconfig, then ran dhclient for athn0 and it
> worked.
Wireless networks are a pain in general, but the general advice is
anyway to make really sure your access point and your client are in fact
using the same settings. On this laptop, my /etc/hostname.iwn0 (not the
same part, I know, but for most practical purposes the same) has only
media autoselect nwid nomap wpakey allfunnybusiness
dhcp
rtsol
> This time i've tried setting chan, bssid, nwid, nwkey, wpakey, and wpaakms.
>
> I've set these parameters with ifconfig, and also entered into my
> /etc/hostname.athn0 file.
I've never had too much joy from setting those explicitly on the client,
but do check what the output of 'ifconfig athn0 scan' says about the
access point's settings, if anything. Worth noting is this bit from the
athn man page:
CAVEATS
The athn driver does not support any of the 802.11n capabilities offered
by the adapters. Additional work is required in ieee80211(9) before
those features can be supported.
which means you will need to stick to a, b or g modes for now.
- P
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://bsdly.blogspot.com/ http://www.bsdly.net/ http://www.nuug.no/
"Remember to set the evil bit on all malicious network traffic"
delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.
