On Tue, Jul 04, 2017 at 10:50:41AM +0300, defanor wrote: > Some of the logs that wpa_supplicant writes are hard to read without > having access to its sources. This one, for instance (copied from > version 2.4, though apparently it's present in 2.6 as well, along with > other similar ones): > > wpa_msg(wpa_s, MSG_INFO, WPA_EVENT_DISCONNECTED "bssid=" MACSTR > " reason=%d locally_generated=1", > MAC2STR(wpa_s->own_addr), WLAN_REASON_DEAUTH_LEAVING); > > A user only sees the error code (with no explanation in the man page), > while a textual message would have been much more useful. These wpa_msg() calls with defined prefixes like that WPA_EVENT_DISCONNECTED are really meant for upper layer programs, not users, to parse.. Such an upper layer component could then convert this to more user friendly indication. -- Jouni Malinen PGP id EFC895FA _______________________________________________ Hostap mailing list Hostap@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/hostap