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>
This commit is contained in:
parent
9ed4076673
commit
c1fb75a6e2
1 changed files with 1 additions and 1 deletions
|
@ -302,7 +302,7 @@ static void radius_client_handle_send_error(struct radius_client_data *radius,
|
||||||
int _errno = errno;
|
int _errno = errno;
|
||||||
wpa_printf(MSG_INFO, "send[RADIUS]: %s", strerror(errno));
|
wpa_printf(MSG_INFO, "send[RADIUS]: %s", strerror(errno));
|
||||||
if (_errno == ENOTCONN || _errno == EDESTADDRREQ || _errno == EINVAL ||
|
if (_errno == ENOTCONN || _errno == EDESTADDRREQ || _errno == EINVAL ||
|
||||||
_errno == EBADF) {
|
_errno == EBADF || _errno == ENETUNREACH) {
|
||||||
hostapd_logger(radius->ctx, NULL, HOSTAPD_MODULE_RADIUS,
|
hostapd_logger(radius->ctx, NULL, HOSTAPD_MODULE_RADIUS,
|
||||||
HOSTAPD_LEVEL_INFO,
|
HOSTAPD_LEVEL_INFO,
|
||||||
"Send failed - maybe interface status changed -"
|
"Send failed - maybe interface status changed -"
|
||||||
|
|
Loading…
Reference in a new issue