[PATCH v2] Write client (dis)associations to a logfile

Jouni Malinen j
Wed Jan 14 16:02:17 PST 2015

On Mon, Jan 12, 2015 at 09:57:37PM +0100, Stefan Tomanek wrote:
> Most embedded system do not have persistent log storage (OpenWrt devices);
> therefore, the list of client actions moves out of the log buffer quite fast.
> And of course syslog messages aren't easily parseble - I am using the written
> logfile to correlate client associations with DHCP leases from dnsmasq. And as
> a last point, the syslog message of a client associating does not include the
> SSID used (which might be interesting on a system servicing multiple networks).
> Using multiple files makes it easier to log each network into separate
> locations; e.g. logging activity in a guest network to /tmp/assoc_guest while
> keeping internal networks away from that log.

I'd rather make the existing syslog mechanism more useful than
introduce something completely new for doing more or less the same
thing. There are too many different existing logging options already..

Jouni Malinen                                            PGP id EFC895FA

More information about the Hostap mailing list