On Thu, Jul 12, 2012 at 05:51:32PM +0200, Stefan Sperling wrote:
Running ifconfig ral0 debug down up can leave slow systems, such
as edd@'s soekris, with an unusable wireless interface until reboot.
The net80211 layer will run a scan when the interface comes up.
The scan hops from channel
Date: Fri, 13 Jul 2012 10:42:02 +0200
From: Stefan Sperling s...@openbsd.org
On Thu, Jul 12, 2012 at 05:51:32PM +0200, Stefan Sperling wrote:
Running ifconfig ral0 debug down up can leave slow systems, such
as edd@'s soekris, with an unusable wireless interface until reboot.
The
+ printf(msg);
This really should be
printf(%s, msg);
To avoid format string problems.
Yes, you say you are completely in control of the string however
someone could reuse this workq handler for some other purpose later.
On Fri, Jul 13, 2012 at 03:16:27AM -0600, Theo de Raadt wrote:
+ printf(msg);
This really should be
printf(%s, msg);
To avoid format string problems.
Yes, you say you are completely in control of the string however
someone could reuse this workq handler for some
Running ifconfig ral0 debug down up can leave slow systems, such
as edd@'s soekris, with an unusable wireless interface until reboot.
The net80211 layer will run a scan when the interface comes up.
The scan hops from channel to channel every 200msec. This hopping is
controlled via a timeout
