Returning to this topic, which has not reached any closure,
investigation reveals that when hostapd is used with the wired driver,
it responds to EAPOL and DHCP messages from the network, but never
independently issues messages to the client network.
If the hostapd configuration is refreshed due to SIGHUP, or it is
terminated via SIGTERM, it does not send a polite deauthentication
message to the authenticated client when the authentication is
cleared. This leaves the client hanging.
Likewise, when hostapd is started, it does not send any messages to
the client network, leaving the authenticated client hanging in a
limbo state where it will continue to try to send packets through the
blocked interface. Only a client which decides to send a EAPOL or
DHCP message will become re-authenticated and thereby unblocked.
I am still searching for the best way to solve this issue. Any useful
opinions are appreciated.
Bob
--
Bob Friesenhahn
bfriesen@xxxxxxxxxxxxxxxxxxx, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer, http://www.GraphicsMagick.org/
_______________________________________________
Hostap mailing list
Hostap@xxxxxxxxxxxxxxxxxxx
http://lists.infradead.org/mailman/listinfo/hostap
