On Wed, January 23, 2013 02:50, slhac tivist wrote: > Thanks for the tip about no 'n' band. Here's some more info: > > Here's my /etc/hostname.athn0 file: > > -wol group egress chan 11 bssid ****** nwid ****** nwkey ****** wpakey > ****** wpaakms pks > dhcp NONE NONE NONE
You're mixing WEP and WPA keys. Try to use one of them, not both. > And here is ifconfig athn0: > > athn0 flag=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 > lladdr: ****** > priority: 4 > groups: wlan egress > media: IEEE802.11 autoselect (DS1 mode 11g) > Status: no network > > And when I scan (sudo ifconfig athn0 scan) I get something like this > (forgot to write down so from memory): > ieee80211: nwid ****** chan 11 bssid ****** 3dB 54MB privacy, > short_preamble, short_slottime > wpakey <not displayed> wpaprotos wpa1, wpa2 wpakms psk wpaciphers tkip, > ccmp wpagroupcipher tkip > inet ****** prefixlen 64 scopeid 0x1 > > Um...when I looked at the router (It's a D-LINK connected to a Telus DSL > box) there is a sticky note on it that says "Wireless: NO DHCP"...but > everyone else is using wireless internet... > > Also , when I scan for networks, not only does the network name appear, but > so does a DLINK and a TELUS network. > > Not sure what other information is relevant. > > MAIN PROBLEM: Athn0 won't link...1/10 times it will it seems, after I > fiddle with it... > > I have a feeling this is a simple config file problem, but I'm just not > used to editing conf files. > > Am I going about this the right way? (i.e. editing /etc/dhclient.conf, > pf.conf, /etc/hostname.athn0, /etc/myname, and running /etc/netstart, > ifconfig, and dhclient?)???? > > Thanks in advance!!! > > On Tue, Jan 22, 2013 at 1:14 PM, Peter N. M. Hansteen <[email protected]>wrote: > >> 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.
