Issues connecting to WPA2-Enterprise Network

[dragoneye]

My ASUS eeePC 1015PX netbook running Sabayon LXDE (also have XFCE installed) has some serious problems when connected to my university's wireless network. The network I am trying to use uses WPA2-Enterprise with PEAP and MSCHAPv2 for security (all running on Cisco networking equipment). I am able to connect to a normal WPA2 home network and have zero issues.

I am using the following wicd template to connect to the network: http://wicd.sourceforge.net/moinmoin/University%20of%20Manitoba%20%28uofm-wpa%20wireless%20network%2C%20WPA2/PEAP%20version%200/MSCHAPv2%29

I am able to connect to the wireless network fine with this template, but I get absolutely terrible network performance which pretty much prevents me from doing anything (1kB/s - 20kB/s, where typical speeds should be in 300kB/s range). Often pages will just fail to load.

My troubleshooting shows that I end up with packet loss in the range of 30-60% when I try and ping a server. Otherwise packets typically have a response <10ms, but on the rare occasion I'll have a packet with a response of 5-7s.

Anyone have any idea why this would be happening?

[Fitzcarraldo]

And this is without fragmentation of packets? I.e., for those packets that do get through, you don't see the message “Frag needed and DF set”?

Irrespective of whether or not you are getting fragmentation of packets, have you played around with the MTU to see if it has an effect?

Code: Select all

ifconfig wlan0 mtu 1464

Code: Select all

ifconfig wlan0 mtu 1492

and so on.

Also, have you tried enabling TCP MTU probing to see if that has an effect?:

Code: Select all

echo 2 > /proc/sys/net/ipv4/tcp_mtu_probing

[dragoneye]

I am not experiencing any fragmentation of packets.

Both changing the MTU and enabling MTU Probing did nothing to solve/improve the issue either.

A couple of other things I have noticed about when this occurs, there are two locations on campus that I have found that the wireless network seems to work ok, but there is nothing about either location that is particularly different from where the problems occur.

Additionally, I noticed that the dropped packets seem to increase a lot when I have any web browser open, even when it is just sitting open with no web pages loaded.