Jouni Malinen ed14b29f38 wpaspy: Do not mark not-existing UNIX domain socket as UDP ... os.stat(path) failure is an ambigious indication of the control interface "path" type (UDP hostname vs. UNIX domain socket path). The path may be a valid UNIX domain socket path, but that socket could have been removed just before reaching here. At least the hwsim test case concurrent_p2pcli managed to hit the "connect exception" print below from UDP handling even when using a UNIX domain socket. Work around incorrect determination of control interface socket type by assuming anything starting with '/' is a UNIX domain socket and not a hostname. Fixes: a2c88a8025 ("wpaspy: Add support for UDP connection") Signed-off-by: Jouni Malinen <jouni@codeaurora.org>		2021-03-01 12:51:20 +02:00
..
Makefile	wpaspy: Allow building with python3	2020-10-11 19:41:08 +03:00
setup.py
test.py	tests: Use python3 compatible print statement	2019-01-26 12:37:25 +02:00
wpaspy.c	wpaspy: Allow building with python3	2020-10-11 19:41:08 +03:00
wpaspy.py	wpaspy: Do not mark not-existing UNIX domain socket as UDP	2021-03-01 12:51:20 +02:00