Thanks for the advice. Yeah, I wasn't sure about using both nwkey and wpakey. I'll try to correct my hostname.if file and get a static ip, and let you know how it goes...
On Wed, Jan 23, 2013 at 1:05 AM, Peter N. M. Hansteen <[email protected]>wrote: > On Tue, Jan 22, 2013 at 04:50:17PM -0700, 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 > > The first thing I notice here is that you specify both wep (nwkey) and wpa > (wpakey etc). > That won't work. Choose one, whatever your access point has. I'd > concentrate on > the basics for now, meaning set only the nwid and either nwkey or wpakey, > see > that you actually have a link, like this iwn0 (status: active) > > [Wed Jan 23 08:59:11] peter@deeperthought:~$ ifconfig iwn0 > iwn0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 > lladdr 00:26:c6:1c:c9:44 > priority: 4 > groups: wlan egress > media: IEEE802.11 autoselect (OFDM54 mode 11g) > status: active > ieee80211: nwid sonofskinny chan 13 bssid 00:12:17:68:8c:e9 207dB > inet6 fe80::226:c6ff:fe1c:c944%iwn0 prefixlen 64 scopeid 0x1 > inet 172.16.103.67 netmask 0xffffff00 broadcast 172.16.103.255 > > > 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 > > This looks like WPA, but do check if that's the one you want. wifi is > rather nasty > in that there's a real risk of interference if there are several access > points > talking on nearby channels, meaning it's higly likely you get random > packet drops > etc even with strong signals. > > > 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... > > it's certainly possible to set up wireless with fixed IP addresses and no > DHCP. > Check if that one is the one you want, if so you will need to get hold of > a valid > fixed IP address and other relevant parameters you would otherwise just be > served > via DHCP. > > > 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... > > from your slightly obfuscated hostname.athn0 it looks like you still have > the > basic parameters wrong. check ifconfig athn0 scan output and go from there > is the best advice. (and of course ifconfig athn0 debug possibly paired > with > creative use of tcpdump could help) > > - Peter > -- > 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.
