NetBSD-Bugs archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: port-evbarm/57308: Raspberry Pi 3 bwfm0 with wpa_supplicant stops working after few hours



On 29/03/2023 11:25, Bartek Krawczyk wrote:
  > From: mlelstv%serpens.de@localhost (Michael van Elst)
  > To: gnats-bugs%netbsd.org@localhost
  > Cc:
  > Subject: Re: port-evbarm/57308: Raspberry Pi 3 bwfm0 with wpa_supplicant stops working after few hours
  > Date: Wed, 29 Mar 2023 08:52:24 -0000 (UTC)
  >
  >   bbartlomiej.mail%gmail.com@localhost writes:
  >
  >   >What helps is to restart wpa_supplicant and sometimes dhcpcd if it doesn't react to this action automatically afterwards.
  >
  >   Can you configure dhcpcd to ignore link states ?
  >
  >   E.g. in /etc/dhcpcd.conf append:
  >
  >   interface bwfm0
  >           nolink
  >
  >
I've added that now. I understand it should help with reacquiring a
  lease after I restart wpa_supplicant? Because during my outage the IP is
  still assigned on the interface and interface is UP with "status: active".

As expected, after dhcpcd update from above suggestion there is no improvement. Today I can't login to the PI3 and on the serial console I still see the IP is there, and wpa_supplicant thinks group rekeying was completed:

rpi3# ifconfig bwfm0
bwfm0: flags=0x8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
ssid "bat cave" nwkey 65536:"",0xbd4e13e244b89677f712e72b404160e8,0x024ad83364a031bc990d75a7cc978ffb,""
        powersave off
        bssid 64:d1:54:ee:0c:fc chan 11
        address: b8:27:eb:e4:30:c8
        media: IEEE802.11 autoselect (VHT mode 11ac)
        status: active
        inet6 fe80::e739:9d49:e1e3:c527%bwfm0/64 flags 0 scopeid 0x3
        inet 192.168.2.212/24 broadcast 192.168.2.255 flags 0

/var/log/messages:

Mar 30 07:05:35 rpi3 wpa_supplicant[672]: bwfm0: WPA: Group rekeying completed with 64:d1:54:ee:0c:fc [GTK=CCMP] Mar 30 07:10:35 rpi3 wpa_supplicant[672]: bwfm0: WPA: Group rekeying completed with 64:d1:54:ee:0c:fc [GTK=CCMP] Mar 30 07:15:35 rpi3 wpa_supplicant[672]: bwfm0: WPA: Group rekeying completed with 64:d1:54:ee:0c:fc [GTK=CCMP] Mar 30 07:05:35 rpi3 wpa_supplicant[672]: bwfm0: WPA: Group rekeying completed with 64:d1:54:ee:0c:fc [GTK=CCMP]
Mar 30 07:35:17 rpi3 syslogd[951]: last message repeated 2 times
Mar 30 07:45:17 rpi3 syslogd[951]: last message repeated 2 times


rpi3# ping 192.168.2.1
PING 192.168.2.1 (192.168.2.1): 56 data bytes
ping: sendto: Host is down
ping: sendto: Host is down
ping: sendto: Host is down
ping: sendto: Host is down
^C
----192.168.2.1 PING Statistics----
4 packets transmitted, 0 packets received, 100.0% packet loss

The PI3 is of course in the same spot, not moved, not touched.
Restarting wpa_supplicant helps:

rpi3# service wpa_supplicant restart
Stopping wpa_supplicant.
Starting wpa_supplicant.
rpi3# ping 192.168.2.1
PING 192.168.2.1 (192.168.2.1): 56 data bytes
64 bytes from 192.168.2.1: icmp_seq=0 ttl=64 time=1.395308 ms
64 bytes from 192.168.2.1: icmp_seq=1 ttl=64 time=1.597339 ms
64 bytes from 192.168.2.1: icmp_seq=2 ttl=64 time=1.534996 ms
64 bytes from 192.168.2.1: icmp_seq=3 ttl=64 time=1.751297 ms
64 bytes from 192.168.2.1: icmp_seq=4 ttl=64 time=1.564996 ms
^C
----192.168.2.1 PING Statistics----
5 packets transmitted, 5 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 1.395308/1.568787/1.751297/0.127844 ms

--
Regards
Bartłomiej Krawczyk



Home | Main Index | Thread Index | Old Index