hi Would /someone/ pretty please fix this "run wpa_supplicant multiple times at interface start" problem?
I'm sure it's screwing things up in a bad way, and trying to grovel around and fix the way we do rc scripts is not my favourite thing in the world. Thanks, -adrian On 24 August 2016 at 13:23, Glen Barber <g...@freebsd.org> wrote: > On Wed, Aug 24, 2016 at 08:19:21PM +0000, Glen Barber wrote: >> On Wed, Aug 24, 2016 at 01:11:21PM -0700, Kevin Oberman wrote: >> > On Aug 24, 2016 12:46 PM, "Glen Barber" <g...@freebsd.org> wrote: >> > >> > > On Wed, Aug 24, 2016 at 12:20:57PM -0700, Kevin Oberman wrote: >> > > > <kob6...@gmail.com> >> > > > On Wed, Aug 24, 2016 at 12:03 PM, Glen Barber <g...@freebsd.org> wrote: >> > > > >> > > > > On Wed, Aug 24, 2016 at 11:55:13AM -0700, Kevin Oberman wrote: >> > > > > > Not working right. I do see 802.11 messages but nothing from iwn. >> > > > > > Rebuilt with: >> > > > > > options IEEE80211_DEBUG >> > > > > > options IWN_DEBUG >> > > > > > >> > > > > > [...] >> > > > > > >> > > > > > Any idea what is going on? >> > > > > >> > > > > Your original email mentions 11.0-BETA4. Are you still running >> > > > > stable/11? If so, could you please update to r304715? If running >> > > > > releng/11.0, the matching commit is r304719. >> > > > > >> > > > >> > > > Since my initial post I have updated to r304734 (running 11-STABLE). I >> > > did >> > > > that before rebuilding my kernel with the DEBUG options as it was >> > > > already >> > > > three weeks old. So this does not seem to have fixed the issue. >> > > >> > > Dumb question, but with reason. >> > > >> > > Does ifconfig(8) actually show wlan0 'UP'? >> > > >> > > I'm asking this because I'm seeing something strange locally on one >> > > machine. >> > > >> > >> > I have been unable to catch it, so I don't know. I know the UP/DOWN >> > sequences in the first log showed many per second and all in the same >> > second. In this case it was UP for 13 seconds, so something was different. >> > >> > I will try to test some more later, but I have to go out for a couple of >> > hours right now. >> > >> >> Ok, thanks. This is different than the issue I'm seeing, part of which >> turned out to be a config issue on one of two machines, but completely >> odd on the other. >> > > Sigh. On my side, it was a config issue on both machines. Sorry for > the noise, but I'm sure you understand my concern and panic this late in > 11.0. > > Glen > _______________________________________________ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
