HOWTO: Wireless Security - WPA1, WPA2, LEAP, etc.

[DieselSnorter]

getting warmer...I'm connected, have an IP. Showing good to excellent signal strength at about 24 MBPS (I can live with that), but I can't get any pages to load.
oy, one thing after another.
I've got my DNS server sent in my resolv.conf...it just doesn't seem to want to pull pages.

I really hope all this mess helps someone else out.

[wieman01]

getting warmer...I'm connected, have an IP. Showing good to excellent signal strength at about 24 MBPS (I can live with that), but I can't get any pages to load.
oy, one thing after another.
I've got my DNS server sent in my resolv.conf...it just doesn't seem to want to pull pages.

I really hope all this mess helps someone else out.

Good. Please issue:

route -n

When you ping your router, do you get a response?

ping 192.168.xxx.xxx

What about Google?

ping www.google.com

[DieselSnorter]

GAH, seems today I'm back to not being able to get an IP address. I'm working on that now. I had one briefly, and tried to get some pages to load, but it was horribly slow. I have 20 MBPS service, and my laptop is moving right along, so I have to think it's the Ubuntu box.

[DieselSnorter]

Okay, I managed to get an IP address for a few minutes, here we go.

route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 wlan1
169.254.0.0 0.0.0.0 255.255.0.0 U 1000 0 0 wlan1
0.0.0.0 192.168.1.100 0.0.0.0 UG 100 0 0 wlan1

PING 192.168.1.100 (192.168.1.100) 56(84) bytes of data.
64 bytes from 192.168.1.100: icmp_seq=1 ttl=64 time=1350 ms
64 bytes from 192.168.1.100: icmp_seq=2 ttl=64 time=353 ms
64 bytes from 192.168.1.100: icmp_seq=3 ttl=64 time=1.61 ms
64 bytes from 192.168.1.100: icmp_seq=4 ttl=64 time=1.67 ms

ping www.google.com
PING www.l.google.com (74.125.47.147) 56(84) bytes of data.
64 bytes from 74.125.47.147: icmp_seq=1 ttl=241 time=25.4 ms
64 bytes from yw-in-f147.google.com (74.125.47.147): icmp_seq=2 ttl=240 time=25.6 ms
64 bytes from yw-in-f147.google.com (74.125.47.147): icmp_seq=3 ttl=241 time=23.1 ms
64 bytes from yw-in-f147.google.com (74.125.47.147): icmp_seq=4 ttl=240 time=1591 ms
64 bytes from yw-in-f147.google.com (74.125.47.147): icmp_seq=5 ttl=240 time=594 ms
64 bytes from yw-in-f147.google.com (74.125.47.147): icmp_seq=6 ttl=241 time=23.7 ms

my syslog has this entry:

DHCPNAK from 192.168.1.100
avahi-autoipd(wlan1)[14518]: no longer a routable address configured, restarting probe process
avai-autoipd(wlan1)[14518] got SIGTERM, quitting.

[wieman01]

GAH, seems today I'm back to not being able to get an IP address. I'm working on that now. I had one briefly, and tried to get some pages to load, but it was horribly slow. I have 20 MBPS service, and my laptop is moving right along, so I have to think it's the Ubuntu box.

Mmm... This looks like a driver issue to me. Your settings are correct, WPA is working fine, however, there is some issue with 'ndiswrapper' if I am not correct. Is your device listed here?

http://ndiswrapper.sourceforge.net/j...id,33/id,list/

Is it listed as a compatible device? Are you on 64-bit Ubuntu?

[DieselSnorter]

pretty sure this is me

Card: Belkin F5D7050B (USB 2.0 Adaptor 802.11b/g 54Mbps) (”version 3000uk” only tested at this time)
Chipset: RT73
usbid: 050d:705A
Driver: Install the drivers for windows included in the box and fetch the .inf files from the installation directory.
Other: Works fine with WPA(PSK-TKIP) using wpa_supplicant on ubuntu 6.06 with ndiswrapper driver. Will freeze the system if removed without ifdown and/or ifconfig down on the device, and even then sometimes. Even though WPA works, I have not yet managed to succeed in using with WEP!

definitely not on 64 bit.

[DieselSnorter]

okay, getting better. I've managed to get online off and on today. So when i connect, I'll do speed tests at random periods. When I first get on, I can pull a solid 12 mbps, that I can live with. After a time it drops to about 6...then to less than 1...then I get disconnected. Is there some file or buffer that is filling up?
I found great improvement when I added my DNS server directly to my Linux machine and didn't rely on it finding my firewall to look for DNS.
Even though I'm keeping my IP over time, my connectivity just seems to quit after a while.

[wieman01]

Again, changing the wireless channel or reducing the default beacon interval (router setting) can help. But it is tough from here to judge what it could be. in my case these 2 settings made the difference and might network has been running smoothly ever since.

Default beacon interval is 40 at the moment.

[DieselSnorter]

I'll give it a shot and see what happens.
Again, a million thanks for all your help with this issue. if you ever make it to Florida, the beer is on me.

[wieman01]

I'll give it a shot and see what happens.
Again, a million thanks for all your help with this issue. if you ever make it to Florida, the beer is on me.

Haha... Thanks, buddy. Nice working with you.