In message <72a5e40f-c973-473c-b2a4-acdd28685...@yahoo.com>, Mark Millard
write
s:
> Cy Schubert wrote on:
> Date: Tue, 01 Jun 2021 14:02:06 -0700 :
>
> > Can you provide me with a backtrace, using the bt command, please.
>
>
> That was in the original message from David W. A copy was
> in the re
Cy Schubert wrote on:
Date: Tue, 01 Jun 2021 14:02:06 -0700 :
> Can you provide me with a backtrace, using the bt command, please.
That was in the original message from David W. A copy was
in the reply that you sent to the list as well:
> > (gdb) bt
> > #0 0x010fb34f in wpa_sm_rx_eapo
Can you provide me with a backtrace, using the bt command, please.
--
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 , David Wolfskill writes:
>
> --+ZZXH3gC
Reading symbols from
/usr/obj/usr/src/amd64.amd64/usr.sbin/wpa/wpa_supplicant/wpa_supplicant...
(No debugging symbols found in
/usr/obj/usr/src/amd64.amd64/usr.sbin/wpa/wpa_supplicant/wpa_supplicant)
[New LWP 100168]
Core was generated by `/usr/sbin/wpa_supplicant -s -B -i wlan0 -c
/etc/wpa_supp
Hi,
Since upgrading servers from 12.2 to 13.0, I get
Fssh_packet_write_wait: Connection to 1.2.3.4 port 22: Broken pipe
consistently, usually after about 11 idle minutes, that's with and
without pf enabled. Client (11.4 in a VM) wasn't altered.
Verbose logging (client and server side) doesn't
