RADIUS client: Handle ENETUNREACH similarly to other failure cases

This is one more possible send() error that should trigger RADIUS server
change if multiple servers are configured.

Signed-off-by: Jouni Malinen <j@w1.fi>

diff --git a/src/radius/radius_client.c b/src/radius/radius_client.c
index 5199da7f470643e2954b3da8c1eb82eeb404fdbf..6049b363e9bdc3cbfd1ae02257d5e04884e3ec01 100644 (file)
--- a/src/radius/radius_client.c
+++ b/src/radius/radius_client.c
@@ -302,7 +302,7 @@ static void radius_client_handle_send_error(struct radius_client_data *radius,
        int _errno = errno;
        wpa_printf(MSG_INFO, "send[RADIUS]: %s", strerror(errno));
        if (_errno == ENOTCONN || _errno == EDESTADDRREQ || _errno == EINVAL ||
-           _errno == EBADF) {
+           _errno == EBADF || _errno == ENETUNREACH) {
                hostapd_logger(radius->ctx, NULL, HOSTAPD_MODULE_RADIUS,
                               HOSTAPD_LEVEL_INFO,
                               "Send failed - maybe interface status changed -"