sorry about that...here's the most recent one: Sep 11 06:31:13 e530c /bsd: iwn0: sending probe_req to 80:2a:a8:57:5e:17 on channel 6 mode 11n Sep 11 06:31:15 e530c ntpd[87584]: DNS lookup tempfail Sep 11 06:31:16 e530c dhclient[9122]: iwn0: writev(DHCPREQUEST): No buffer space available Sep 11 06:31:18 e530c /bsd: iwn0: RUN -> SCAN Sep 11 06:31:18 e530c /bsd: iwn0: end active scan Sep 11 06:31:18 e530c /bsd: iwn0: - 00:0d:67:7d:a9:43 1 +172 54M ess no! rsn! "CableWiFi"! Sep 11 06:31:18 e530c /bsd: iwn0: - 08:86:3b:b6:2f:80 1 +182 54M ess privacy rsn "belkin.f80"! ...
On Wed, Sep 11, 2019 at 7:53 AM Stefan Sperling <s...@stsp.name> wrote: > > On Wed, Sep 11, 2019 at 12:16:06AM -0700, Bryan Stenson wrote: > > doh...I don't know why I didn't think of that... > > > > Good news, with 'ifconfig iwn0 debug' set, once the strange behavior > > starts, I see LOTS of repeated messages, the pattern happens about > > once every 4 seconds, and dumps the following into /var/log/messages: > > > > ... > > # continuous spamming of /var/log/messages from after the network has > > been in the troubled/failed state for a while > > You snipped the exciting part. > > I need to know why it decides to do a transition of the form: > > RUN -> something > > This should be somewhere at the top of this stream of output.
