Re: Frequent network drops (NM, FC29)?

[Shawn Adams <shawn_adams web de>]

Derek,

I'll preface this by stating I'm no progammer, or expert on NM.

I didn't see any response, this looks like wpa_supplicant and the chip
didn't communicate -


Right after CTRL-EVENT-CONNECTED, I usually see something like this,
never bgscan messages.

May  5 11:31:43 Tuxedo1 wpa_supplicant[1231]: wlp2s0:
CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-66 noise=9999 txrate=360000

Laptop works, then i roam down the hall :

May  5 11:36:16 Tuxedo1 wpa_supplicant[1231]: wlp2s0:
CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-80 noise=9999 txrate=216000
May  5 11:36:21 Tuxedo1 wpa_supplicant[1231]: wlp2s0: SME: Trying to
authenticate with 00:a3:01:15:77:30 (SSID='SSIDFAKE' freq=5180 MHz)
May  5 11:36:21 Tuxedo1 kernel: [208916.885771] wlp2s0: disconnect from
AP 44:33:22:db:13:70 for new auth to 33:99:1e:11:77:30
May  5 11:36:21 Tuxedo1 kernel: [208916.889414] wlp2s0: authenticate
with 88:99:11:00:77:30


I don't think that's an 802.11 problem, but a driver or supplicant
problem, bgscan simple didn't get data from the driver (wild guess). I'd
check the actual 802.11 connection at the time this happens out of
curiosity:

root@Tuxedo1:/var/log# iw wlp2s0 link
Connected to ac:a3:1e:db:14:70 (on wlp2s0)
    SSID: SSIDFAKE
    freq: 5220
    RX: 1618469 bytes (1151 packets)
    TX: 188412 bytes (953 packets)
    signal: -61 dBm
    tx bitrate: 360.0 MBit/s VHT-MCS 8 40MHz short GI VHT-NSS 2
    bss flags:    short-slot-time
    dtim period:    1
    beacon int:    100

Hope this helps.




On 29.04.19 16:28, Derek Atkins wrote:
> HI,
>
> I'm having an issue on my Fedora-29 laptop where my Wifi shows periodic
> network drops.  I'm running mtr and it's working fine, but then it
> effectively stops transmitting packets for a few seconds, and then it
> starts up again.  This pause coincides with the following entries in my
> /var/log/messages:
>
> Apr 29 10:23:25 securerf wpa_supplicant[1899]: wlp0s20f0u2: CTRL-EVENT-DISCONNECTED bssid=dc:7f:a4:67:5a:a5 
> reason=0
> Apr 29 10:23:25 securerf wpa_supplicant[1899]: wlp0s20f0u2: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
> Apr 29 10:23:25 securerf wpa_supplicant[1899]: wlp0s20f0u2: CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY 
> alpha2=US
> Apr 29 10:23:33 securerf wpa_supplicant[1899]: wlp0s20f0u2: Trying to associate with dc:7f:a4:67:5a:a5 
> (SSID='ATT234H8Fp' freq=2462 MHz)
> Apr 29 10:23:33 securerf wpa_supplicant[1899]: wlp0s20f0u2: Associated with dc:7f:a4:67:5a:a5
> Apr 29 10:23:33 securerf wpa_supplicant[1899]: wlp0s20f0u2: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
> Apr 29 10:23:33 securerf wpa_supplicant[1899]: wlp0s20f0u2: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE 
> type=COUNTRY alpha2=US
> Apr 29 10:23:33 securerf wpa_supplicant[1899]: wlp0s20f0u2: WPA: Key negotiation completed with 
> dc:7f:a4:67:5a:a5 [PTK=CCMP GTK=CCMP]
> Apr 29 10:23:33 securerf wpa_supplicant[1899]: wlp0s20f0u2: CTRL-EVENT-CONNECTED - Connection to 
> dc:7f:a4:67:5a:a5 completed [id=0 id_str=]
> Apr 29 10:23:33 securerf wpa_supplicant[1899]: bgscan simple: Failed to enable signal strength monitoring
>
> Any ideas how to debug or, better yet, fix this?  I have already
> rebooted my wifi router.  I am sitting 15-20 feet away with an almost
> direct line-of sight, but I can literally be sitting 3 feet away and
> still have this issue.  Other systems on my network don't appear have
> this kind of issue.
>
> Thanks,
>
> -derek