On 03/23/2017 05:40 PM, Ian Malone wrote: > On 12 January 2017 at 05:04, Chris Murphy <lists@xxxxxxxxxxxxxxxxx> wrote: >> Damn strange. >> >> The computer is in a static location for all tests. This is still using >> iperf in all cases, but abbreviated since I'm copying by hand. Each test is >> about five seconds apart. >> >> Fedora 25 live >> 58 Mbit/sec >> 61 >> 41 >> >> Fedora 24 live >> 54 Mbit/sec >> 46 >> 38 >> 65 >> >> Fedora 25 installed >> 29 >> 42 >> 38 >> 38 >> co >> There are a total of three wireless devices connected to this AP. All are >> connected at the same time but only the test client is actively being used >> when the testing is happening. But it's in an apartment building, with >> hundreds of units all of which have wireless APs. >> > > Did anyone get to the bottom of this? I installed F25 a couple of > weeks ago and network performance is noticeably poorer on this > machine. When browsing the internet, or particularly on Ajax based > sites like gmail or google search connections seem to just drop. The > previous Fedora that was on this machine (23 I think) was fine, and my > laptop (still on an older Fedora) and other devices have not > experienced any change. Looking in journalctl as root I see frequent > renegotiation with the AP, e.g.: > Mar 24 00:21:29 atlas wpa_supplicant[864]: wlp2s0: SME: Trying to > authenticate with xx:xx:xx:xx:xx:xx (SSID='X' freq=5200 MHz) > Mar 24 00:21:29 atlas kernel: wlp2s0: disconnect from AP > xx:xx:xx:xx:xx:xx for new auth to 00:a4:23:17:18:e5 > Mar 24 00:21:29 atlas kernel: wlp2s0: authenticate with xx:xx:xx:xx:xx:xx > Mar 24 00:21:29 atlas kernel: wlp2s0: send auth to xx:xx:xx:xx:xx:xx (try 1/3) > Mar 24 00:21:29 atlas kernel: wlp2s0: authenticated > Mar 24 00:21:29 atlas kernel: wlp2s0: associate with xx:xx:xx:xx:xx:xx (try 1/3) > Mar 24 00:21:29 atlas wpa_supplicant[864]: wlp2s0: Trying to associate > with xx:xx:xx:xx:xx:xx (SSID='X' freq=5200 MHz) > While the machine is supposedly connected. > > There's also this, > Mar 24 00:21:29 atlas systemd-udevd[5658]: Process '/usr/sbin/crda' > failed with exit code 249. > which can't be a good sign. The first things I'd do is see what hardware you actually have: # lspci | grep -i wireless Then see which driver your wifi is using via # ethtool -i wlp2s0 See if perhaps there's another driver or perhaps newer firmware you can use for that chipset. Sometimes the kernel or udev don't necessarily make the right decisions about which driver to use. My F25 machines with wifi are both using the iwlwifi driver (both use Intel wireless chips): (Desktop) # lspci | grep -i wireless 04:00.0 Network controller: Intel Corporation Wireless 3165 (rev 81) #ethtool -i wlp4s0 driver: iwlwifi version: 4.9.13-201.fc25.x86_64 firmware-version: 22.361476.0 ... (Laptop) # lspci | grep -i wireless 01:00.0 Network controller: Intel Corporation Centrino Wireless-N 1030 [Rainbow Peak] (rev 34) # ethtool -i wlan0 driver: iwlwifi version: 4.9.14-200.fc25.x86_64 firmware-version: 18.168.6.1 ... I've had no issues with performance or the ability to stay connected and the laptop goes LOTS of places with me. ---------------------------------------------------------------------- - Rick Stevens, Systems Engineer, AllDigital ricks@xxxxxxxxxxxxxx - - AIM/Skype: therps2 ICQ: 226437340 Yahoo: origrps2 - - - - Duct Tape + Magic Marker = Label Maker! - ---------------------------------------------------------------------- _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
