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

[Bartek Krawczyk <bbartlomiej.mail%gmail.com@localhost>]

The following reply was made to PR port-evbarm/57308; it has been noted by GNATS.

From: Bartek Krawczyk <bbartlomiej.mail%gmail.com@localhost>
To: gnats-bugs%netbsd.org@localhost, port-evbarm-maintainer%netbsd.org@localhost,
 gnats-admin%netbsd.org@localhost, netbsd-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 11:23:32 +0200

 On 29/03/2023 10:55, Michael van Elst wrote:
 > The following reply was made to PR port-evbarm/57308; it has been noted by GNATS.
 > 
 > 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".
 
 -- 
 Regards
 BartÅ?omiej Krawczyk