Re: wlan0 no longer functional after n249128-a0c64a443e4c -> n249146-cb5c07649aa0

2021-09-08 Thread Cy Schubert
In message <86ilzaoc0z@shiori.com.br>, Filipe da Silva Santos via current w rites: > Hi, thank you for the support, and sorry for the late feedback. > > The procedure `wpa_poststart' didn't solve the regression on my system. > wlan0 doesn't seem to come up. > > I have the following output on

Re: wlan0 no longer functional after n249128-a0c64a443e4c -> n249146-cb5c07649aa0

2021-09-08 Thread Filipe da Silva Santos via current
Hi, thank you for the support, and sorry for the late feedback. The procedure `wpa_poststart' didn't solve the regression on my system. wlan0 doesn't seem to come up. I have the following output on my log: | Sep 8 19:09:43 misaka wpa_supplicant[23325]: ioctl[SIOCS80211, op=103, val=0,

Re: wlan0 no longer functional after n249128-a0c64a443e4c -> n249146-cb5c07649aa0

2021-09-08 Thread Cy Schubert
Sorry for the breakage. -- Cheers, Cy Schubert FreeBSD UNIX: Web: https://FreeBSD.org NTP: Web: https://nwtime.org The need of the many outweighs the greed of the few. In message , Idwer Vollering writes: > I can confirm this commit has addressed the

Re: wlan0 no longer functional after n249128-a0c64a443e4c -> n249146-cb5c07649aa0

2021-09-08 Thread Idwer Vollering
I can confirm this commit has addressed the wpa_supplicant 'breakage'. Thanks for fixing it. Op di 7 sep. 2021 om 19:37 schreef Cy Schubert : > > In message , David Wolfskill writes: > > -- > Cheers, > Cy Schubert > FreeBSD UNIX: Web: https://FreeBSD.org > NTP: Web:

Re: wlan0 no longer functional after n249128-a0c64a443e4c -> n249146-cb5c07649aa0

2021-09-07 Thread Cy Schubert
In message , David Wolfskill writes: -- Cheers, Cy Schubert FreeBSD UNIX: Web: https://FreeBSD.org NTP: Web: https://nwtime.org The need of the many outweighs the greed of the few. > On Tue, Sep 07, 2021 at 10:13:23AM +0200, Jakob Alvermark wrote: > > ...=20 > >

Re: wlan0 no longer functional after n249128-a0c64a443e4c -> n249146-cb5c07649aa0

2021-09-07 Thread David Wolfskill
On Tue, Sep 07, 2021 at 10:13:23AM +0200, Jakob Alvermark wrote: > ... > wlan0 does not associate after boot. (This is with iwm, AC 9260) > > My workaround is simply 'ifconfig wlan0 up'. > > After a few seconds wpa_supplicant associates and another few secods > later I have a DHCP IP address.

Re: wlan0 no longer functional after n249128-a0c64a443e4c -> n249146-cb5c07649aa0

2021-09-07 Thread Jakob Alvermark
On 9/6/21 8:21 PM, Cy Schubert wrote: In message <2780735.ssxfcku...@sigill.theweb.org.ua>, "Oleg V. Nauman" writes: On 2021 M09 6, Mon 20:31:33 EEST Cy Schubert wrote: One last favour to ask, can you try this with the wpa_supplicant-devel port, please? I'm trying to narrow down if this is

Re: wlan0 no longer functional after n249128-a0c64a443e4c -> n249146-cb5c07649aa0

2021-09-06 Thread Cy Schubert
In message <86tuix4cys@shiori.com.br>, Filipe da Silva Santos writes: > --=-=-= > Content-Type: text/plain > Content-Transfer-Encoding: quoted-printable > > > I'll have more questions later (need to start working on another job) but= > =20 > > I'd like to learn more about your configuration to

Re: wlan0 no longer functional after n249128-a0c64a443e4c -> n249146-cb5c07649aa0

2021-09-06 Thread Filipe da Silva Santos via current
> I'll have more questions later (need to start working on another job) but > I'd like to learn more about your configuration to understand why it works > at boot for myself and phlip@ and not for you and the others here on > -current who have experienced the same issue. Understanding what

Re: wlan0 no longer functional after n249128-a0c64a443e4c -> n249146-cb5c07649aa0

2021-09-06 Thread Cy Schubert
In message <2780735.ssxfcku...@sigill.theweb.org.ua>, "Oleg V. Nauman" writes: > On 2021 M09 6, Mon 20:31:33 EEST Cy Schubert wrote: > > One last favour to ask, can you try this with the wpa_supplicant-devel > > port, please? I'm trying to narrow down if this is related to the options > > in

Re: wlan0 no longer functional after n249128-a0c64a443e4c -> n249146-cb5c07649aa0

2021-09-06 Thread Oleg V. Nauman
On 2021 M09 6, Mon 20:31:33 EEST Cy Schubert wrote: > One last favour to ask, can you try this with the wpa_supplicant-devel > port, please? I'm trying to narrow down if this is related to the options > in usr.sbin/wpa/Makefile.inc or an upstream problem. If this behaves the > same using

Re: wlan0 no longer functional after n249128-a0c64a443e4c -> n249146-cb5c07649aa0

2021-09-06 Thread Cy Schubert
One last favour to ask, can you try this with the wpa_supplicant-devel port, please? I'm trying to narrow down if this is related to the options in usr.sbin/wpa/Makefile.inc or an upstream problem. If this behaves the same using wpa_supplicant-devel, this tells me to look at the code instead

Re: wlan0 no longer functional after n249128-a0c64a443e4c -> n249146-cb5c07649aa0

2021-09-06 Thread Oleg V. Nauman
On 2021 M09 6, Mon 18:41:13 EEST Cy Schubert wrote: > I changed mine to be the same as yours. I can connect. (I use iwn(4) and > ath(4) here.) a ) regular reboot - wlan can not associate b ) service netif restart - wlan can not associate c ) service netif stop wlan0 ; service netif start wlan0

Re: wlan0 no longer functional after n249128-a0c64a443e4c -> n249146-cb5c07649aa0

2021-09-06 Thread Oleg V. Nauman
On 2021 M09 6, Mon 08:50:21 EEST Cy Schubert wrote: > In message <2838567.hhqauc6...@sigill.theweb.org.ua>, "Oleg V. Nauman" > > writes: > > On 2021 M09 5, Sun 15:52:50 EEST David Wolfskill wrote: > > > Sorry I hadn't noticed this yesterday (so I could have repported it > > > then), but after

Re: wlan0 no longer functional after n249128-a0c64a443e4c -> n249146-cb5c07649aa0

2021-09-06 Thread Oleg V. Nauman
On 2021 M09 6, Mon 16:23:21 EEST Cy Schubert wrote: > In message om> > > , Idwer Vollering writes: > > Op ma 6 sep. 2021 om 07:53 schreef Cy Schubert : > > > In message <2838567.hhqauc6...@sigill.theweb.org.ua>, "Oleg V. Nauman" > > > > > > writes: > > > > On 2021 M09 5, Sun 15:52:50 EEST

Re: wlan0 no longer functional after n249128-a0c64a443e4c -> n249146-cb5c07649aa0

2021-09-06 Thread Cy Schubert
I changed mine to be the same as yours. I can connect. (I use iwn(4) and ath(4) here.) Do you reboot every time you test or simply this? service netif stop wlan0 service netif start wlan0 If simply above, does a reboot have it work again? The reason I ask is, I discovered,

Re: wlan0 no longer functional after n249128-a0c64a443e4c -> n249146-cb5c07649aa0

2021-09-06 Thread Idwer Vollering
There's no core dump in /, wpa_supplicant connects to 802.11b/g/n (there's no way to lock this, instead of having a mix of standards) on 2,4GHz. /etc/wpa_supplicant.conf: network={ ssid="some ssid" scan_ssid=1 key_mgmt=WPA-PSK psk="some key" } Op ma 6 sep. 2021 om 15:23 schreef Cy Schubert : > >

Re: wlan0 no longer functional after n249128-a0c64a443e4c -> n249146-cb5c07649aa0

2021-09-06 Thread Cy Schubert
In message , Idwer Vollering writes: > Op ma 6 sep. 2021 om 07:53 schreef Cy Schubert : > > > > In message <2838567.hhqauc6...@sigill.theweb.org.ua>, "Oleg V. Nauman" > > writes: > > > On 2021 M09 5, Sun 15:52:50 EEST David Wolfskill wrote: > > > > Sorry I hadn't noticed this yesterday (so I

Re: wlan0 no longer functional after n249128-a0c64a443e4c -> n249146-cb5c07649aa0

2021-09-06 Thread Idwer Vollering
Op ma 6 sep. 2021 om 07:53 schreef Cy Schubert : > > In message <2838567.hhqauc6...@sigill.theweb.org.ua>, "Oleg V. Nauman" > writes: > > On 2021 M09 5, Sun 15:52:50 EEST David Wolfskill wrote: > > > Sorry I hadn't noticed this yesterday (so I could have repported it > > > then), but after

wlan0 functional for me with n249159-bb61ccd530b (was: wlan0 no longer functional after n249128-a0c64a443e4c -> n249146-cb5c07649aa0)

2021-09-06 Thread Graham Perrin
On 05/09/2021 14:36, David Wolfskill wrote: a reality check would almost certainly be helpful. :-) No problem here; . n248984-08b9cc316a3 (2021-08-28) upgraded to n249159-bb61ccd530b (2021-09-05),

Re: wlan0 no longer functional after n249128-a0c64a443e4c -> n249146-cb5c07649aa0

2021-09-05 Thread Cy Schubert
In message <2838567.hhqauc6...@sigill.theweb.org.ua>, "Oleg V. Nauman" writes: > On 2021 M09 5, Sun 15:52:50 EEST David Wolfskill wrote: > > Sorry I hadn't noticed this yesterday (so I could have repported it > > then), but after updating the "head" slice of my laptopp from: > > > > FreeBSD

Re: wlan0 no longer functional after n249128-a0c64a443e4c -> n249146-cb5c07649aa0

2021-09-05 Thread Oleg V. Nauman
On 2021 M09 5, Sun 15:52:50 EEST David Wolfskill wrote: > Sorry I hadn't noticed this yesterday (so I could have repported it > then), but after updating the "head" slice of my laptopp from: > > FreeBSD g1-51.catwhisker.org 14.0-CURRENT FreeBSD 14.0-CURRENT #340 > main-n249128-a0c64a443e4c: Fri

Re: wlan0 no longer functional after n249128-a0c64a443e4c -> n249146-cb5c07649aa0

2021-09-05 Thread David Wolfskill
On Sun, Sep 05, 2021 at 02:22:58PM +0100, Graham Perrin wrote: > > > … I note that the subject update also included updates to > > contrib/wpa/wpa_supplicant, as well as some files in sys/net80211, > > but I have not started chasing that down. … > > Can you share relevant lines from your

Re: wlan0 no longer functional after n249128-a0c64a443e4c -> n249146-cb5c07649aa0

2021-09-05 Thread Graham Perrin
On 05/09/2021 13:52, David Wolfskill wrote: … from: FreeBSD g1-51.catwhisker.org 14.0-CURRENT FreeBSD 14.0-CURRENT #340 main-n249128-a0c64a443e4c: Fri Sep 3 04:06:12 PDT 2021r...@g1-55.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/CANARY amd64 1400032 1400032 to: FreeBSD

wlan0 no longer functional after n249128-a0c64a443e4c -> n249146-cb5c07649aa0

2021-09-05 Thread David Wolfskill
Sorry I hadn't noticed this yesterday (so I could have repported it then), but after updating the "head" slice of my laptopp from: FreeBSD g1-51.catwhisker.org 14.0-CURRENT FreeBSD 14.0-CURRENT #340 main-n249128-a0c64a443e4c: Fri Sep 3 04:06:12 PDT 2021