5GHz Wifi can not renew DHCP-Lease at 06:30 am

Hello together,

I am using OpenWrt on three Linksys 3200ACM Routers and all of them have the same six wifi networks. I am using OpenWrt 18.06.5 (latest firmware). Three of the wifi-network are 5GHz networks ans the other three networks are 2.4 GHz networks. Four networks are encrypted with wpa2-psk and two networks are encrypted with wpa2-eap. Only one network is making problems and this is the 5GHz network with wpa2-eap encryption. It disconnects after about 12 hours and always around 06:30 am. The same 2.4 GHz network with wpa2-eap encryption does not have this problem.

option eap_reauth_period '0' is already set.

Can you help me?

Greetings
Justin Afzal

Is there anything suspicious in the logs? logread
What is the configuration? uci export network; uci export dhcp; uci export wireless
Did you add any cronjobs?
Does it come back to normal if you reload the wifi or do you have to reboot the router?

Hi trendy,

I am not using the DHCP service from the Router. This is our wifi-config:

config wifi-iface
	option device 'radio0'
	option mode 'ap'
	option ssid '5GHz-Wifi'
	option network '115_RADIUS'
	option disassoc_low_ack '0'
	option encryption 'wpa2+ccmp'
	option auth_server 'XXX'
	option auth_secret 'XXX'
	option eap_reauth_period '0'

This is the log with debug enabled (part, when the disconnect happend):

Fri Dec 20 06:59:15 2019 daemon.debug hostapd: wlan0: STA 40:a3:cc:a6:a2:25 IEEE 802.1X: received EAPOL-Start from STA
Fri Dec 20 06:59:15 2019 daemon.debug hostapd: wlan0: STA 40:a3:cc:a6:a2:25 WPA: event 5 notification
Fri Dec 20 06:59:15 2019 daemon.notice hostapd: wlan0: CTRL-EVENT-EAP-STARTED 40:a3:cc:a6:a2:25
Fri Dec 20 06:59:15 2019 daemon.notice hostapd: wlan0: CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=1
Fri Dec 20 06:59:15 2019 daemon.debug hostapd: wlan0: STA 40:a3:cc:a6:a2:25 IEEE 802.1X: Sending EAP Packet (identifier 103)
Fri Dec 20 06:59:15 2019 daemon.debug hostapd: wlan0: STA 40:a3:cc:a6:a2:25 IEEE 802.1X: received EAP packet (code=2 id=103 len=20) from STA: EAP Response-Identity (1)
Fri Dec 20 06:59:15 2019 daemon.debug hostapd: wlan0: STA 40:a3:cc:a6:a2:25 IEEE 802.1X: STA identity 'XXX'
Fri Dec 20 06:59:15 2019 daemon.debug hostapd: wlan0: RADIUS Sending RADIUS message to authentication server
Fri Dec 20 06:59:15 2019 daemon.debug hostapd: wlan0: RADIUS Next RADIUS client retransmit in 3 seconds
Fri Dec 20 06:59:15 2019 daemon.debug hostapd: wlan0: RADIUS Received 90 bytes from RADIUS server
Fri Dec 20 06:59:15 2019 daemon.debug hostapd: wlan0: RADIUS Received RADIUS message
Fri Dec 20 06:59:15 2019 daemon.debug hostapd: wlan0: STA 40:a3:cc:a6:a2:25 RADIUS: Received RADIUS packet matched with a pending request, round trip time 0.26 sec
Fri Dec 20 06:59:15 2019 daemon.debug hostapd: wlan0: STA 40:a3:cc:a6:a2:25 IEEE 802.1X: using EAP timeout of 30 seconds (from RADIUS)
Fri Dec 20 06:59:15 2019 daemon.debug hostapd: wlan0: STA 40:a3:cc:a6:a2:25 IEEE 802.1X: decapsulated EAP packet (code=1 id=104 len=6) from RADIUS server: EAP-Request-TLS (13)
Fri Dec 20 06:59:15 2019 daemon.debug hostapd: wlan0: STA 40:a3:cc:a6:a2:25 IEEE 802.1X: Sending EAP Packet (identifier 104)
Fri Dec 20 06:59:15 2019 daemon.debug hostapd: wlan0: STA 40:a3:cc:a6:a2:25 IEEE 802.1X: received EAP packet (code=2 id=104 len=166) from STA: EAP Response-TLS (13)
Fri Dec 20 06:59:15 2019 daemon.debug hostapd: wlan0: RADIUS Sending RADIUS message to authentication server
Fri Dec 20 06:59:15 2019 daemon.debug hostapd: wlan0: RADIUS Next RADIUS client retransmit in 3 seconds
Fri Dec 20 06:59:15 2019 daemon.debug hostapd: wlan0: RADIUS Received 1490 bytes from RADIUS server
Fri Dec 20 06:59:15 2019 daemon.debug hostapd: wlan0: RADIUS Received RADIUS message
Fri Dec 20 06:59:15 2019 daemon.debug hostapd: wlan0: STA 40:a3:cc:a6:a2:25 RADIUS: Received RADIUS packet matched with a pending request, round trip time 0.01 sec
Fri Dec 20 06:59:15 2019 daemon.debug hostapd: wlan0: STA 40:a3:cc:a6:a2:25 IEEE 802.1X: using EAP timeout of 30 seconds (from RADIUS)
Fri Dec 20 06:59:15 2019 daemon.debug hostapd: wlan0: STA 40:a3:cc:a6:a2:25 IEEE 802.1X: decapsulated EAP packet (code=1 id=105 len=1396) from RADIUS server: EAP-Request-TLS (13)
Fri Dec 20 06:59:15 2019 daemon.debug hostapd: wlan0: STA 40:a3:cc:a6:a2:25 IEEE 802.1X: Sending EAP Packet (identifier 105)
Fri Dec 20 06:59:15 2019 daemon.debug hostapd: wlan0: STA 40:a3:cc:a6:a2:25 IEEE 802.1X: received EAP packet (code=2 id=105 len=6) from STA: EAP Response-TLS (13)
Fri Dec 20 06:59:15 2019 daemon.debug hostapd: wlan0: RADIUS Sending RADIUS message to authentication server
Fri Dec 20 06:59:15 2019 daemon.debug hostapd: wlan0: RADIUS Next RADIUS client retransmit in 3 seconds
Fri Dec 20 06:59:15 2019 daemon.debug hostapd: wlan0: RADIUS Received 194 bytes from RADIUS server
Fri Dec 20 06:59:15 2019 daemon.debug hostapd: wlan0: RADIUS Received RADIUS message
Fri Dec 20 06:59:15 2019 daemon.debug hostapd: wlan0: STA 40:a3:cc:a6:a2:25 RADIUS: Received RADIUS packet matched with a pending request, round trip time 0.00 sec
Fri Dec 20 06:59:15 2019 daemon.debug hostapd: wlan0: STA 40:a3:cc:a6:a2:25 IEEE 802.1X: using EAP timeout of 30 seconds (from RADIUS)
Fri Dec 20 06:59:15 2019 daemon.debug hostapd: wlan0: STA 40:a3:cc:a6:a2:25 IEEE 802.1X: decapsulated EAP packet (code=1 id=106 len=110) from RADIUS server: EAP-Request-TLS (13)
Fri Dec 20 06:59:15 2019 daemon.debug hostapd: wlan0: STA 40:a3:cc:a6:a2:25 IEEE 802.1X: Sending EAP Packet (identifier 106)
Fri Dec 20 06:59:15 2019 daemon.debug hostapd: wlan0: STA 40:a3:cc:a6:a2:25 IEEE 802.1X: received EAP packet (code=2 id=106 len=1492) from STA: EAP Response-TLS (13)
Fri Dec 20 06:59:15 2019 daemon.debug hostapd: wlan0: RADIUS Sending RADIUS message to authentication server
Fri Dec 20 06:59:15 2019 daemon.debug hostapd: wlan0: RADIUS Next RADIUS client retransmit in 3 seconds
Fri Dec 20 06:59:15 2019 daemon.debug hostapd: wlan0: RADIUS Received 90 bytes from RADIUS server
Fri Dec 20 06:59:15 2019 daemon.debug hostapd: wlan0: RADIUS Received RADIUS message
Fri Dec 20 06:59:15 2019 daemon.debug hostapd: wlan0: STA 40:a3:cc:a6:a2:25 RADIUS: Received RADIUS packet matched with a pending request, round trip time 0.00 sec
Fri Dec 20 06:59:15 2019 daemon.debug hostapd: wlan0: STA 40:a3:cc:a6:a2:25 IEEE 802.1X: using EAP timeout of 30 seconds (from RADIUS)
Fri Dec 20 06:59:15 2019 daemon.debug hostapd: wlan0: STA 40:a3:cc:a6:a2:25 IEEE 802.1X: decapsulated EAP packet (code=1 id=107 len=6) from RADIUS server: EAP-Request-TLS (13)
Fri Dec 20 06:59:15 2019 daemon.debug hostapd: wlan0: STA 40:a3:cc:a6:a2:25 IEEE 802.1X: Sending EAP Packet (identifier 107)
Fri Dec 20 06:59:15 2019 daemon.debug hostapd: wlan0: STA 40:a3:cc:a6:a2:25 IEEE 802.1X: received EAP packet (code=2 id=107 len=190) from STA: EAP Response-TLS (13)
Fri Dec 20 06:59:15 2019 daemon.debug hostapd: wlan0: RADIUS Sending RADIUS message to authentication server
Fri Dec 20 06:59:15 2019 daemon.debug hostapd: wlan0: RADIUS Next RADIUS client retransmit in 3 seconds
Fri Dec 20 06:59:15 2019 daemon.debug hostapd: wlan0: RADIUS Received 153 bytes from RADIUS server
Fri Dec 20 06:59:15 2019 daemon.debug hostapd: wlan0: RADIUS Received RADIUS message
Fri Dec 20 06:59:15 2019 daemon.debug hostapd: wlan0: STA 40:a3:cc:a6:a2:25 RADIUS: Received RADIUS packet matched with a pending request, round trip time 0.18 sec
Fri Dec 20 06:59:15 2019 daemon.debug hostapd: wlan0: STA 40:a3:cc:a6:a2:25 IEEE 802.1X: using EAP timeout of 30 seconds (from RADIUS)
Fri Dec 20 06:59:15 2019 daemon.debug hostapd: wlan0: STA 40:a3:cc:a6:a2:25 IEEE 802.1X: decapsulated EAP packet (code=1 id=108 len=69) from RADIUS server: EAP-Request-TLS (13)
Fri Dec 20 06:59:15 2019 daemon.debug hostapd: wlan0: STA 40:a3:cc:a6:a2:25 IEEE 802.1X: Sending EAP Packet (identifier 108)
Fri Dec 20 06:59:15 2019 daemon.debug hostapd: wlan0: STA 40:a3:cc:a6:a2:25 IEEE 802.1X: received EAP packet (code=2 id=108 len=6) from STA: EAP Response-TLS (13)
Fri Dec 20 06:59:15 2019 daemon.debug hostapd: wlan0: RADIUS Sending RADIUS message to authentication server
Fri Dec 20 06:59:15 2019 daemon.debug hostapd: wlan0: RADIUS Next RADIUS client retransmit in 3 seconds
Fri Dec 20 06:59:15 2019 daemon.debug hostapd: wlan0: RADIUS Received 250 bytes from RADIUS server
Fri Dec 20 06:59:15 2019 daemon.debug hostapd: wlan0: RADIUS Received RADIUS message
Fri Dec 20 06:59:15 2019 daemon.debug hostapd: wlan0: STA 40:a3:cc:a6:a2:25 RADIUS: Received RADIUS packet matched with a pending request, round trip time 0.00 sec
Fri Dec 20 06:59:15 2019 daemon.debug hostapd: wlan0: STA 40:a3:cc:a6:a2:25 IEEE 802.11: binding station to interface 'wlan0'
Fri Dec 20 06:59:15 2019 daemon.debug hostapd: wlan0: STA 40:a3:cc:a6:a2:25 IEEE 802.1X: decapsulated EAP packet (code=3 id=108 len=4) from RADIUS server: EAP Success
Fri Dec 20 06:59:15 2019 daemon.notice hostapd: wlan0: CTRL-EVENT-EAP-SUCCESS2 40:a3:cc:a6:a2:25
Fri Dec 20 06:59:15 2019 daemon.debug hostapd: wlan0: STA 40:a3:cc:a6:a2:25 IEEE 802.1X: Sending EAP Packet (identifier 108)
Fri Dec 20 06:59:15 2019 daemon.debug hostapd: wlan0: STA 40:a3:cc:a6:a2:25 IEEE 802.1X: authorizing port
Fri Dec 20 06:59:15 2019 daemon.info hostapd: wlan0: STA 40:a3:cc:a6:a2:25 RADIUS: starting accounting session 6D5C0BB3BF4B711F
Fri Dec 20 06:59:15 2019 daemon.info hostapd: wlan0: STA 40:a3:cc:a6:a2:25 IEEE 802.1X: authenticated - EAP type: 13 (TLS)
Fri Dec 20 06:59:15 2019 daemon.debug hostapd: wlan0: STA 40:a3:cc:a6:a2:25 WPA: sending 1/4 msg of 4-Way Handshake
Fri Dec 20 06:59:15 2019 daemon.debug hostapd: wlan0: STA 40:a3:cc:a6:a2:25 WPA: received EAPOL-Key frame (2/4 Pairwise)
Fri Dec 20 06:59:15 2019 daemon.debug hostapd: wlan0: STA 40:a3:cc:a6:a2:25 WPA: sending 3/4 msg of 4-Way Handshake
Fri Dec 20 06:59:15 2019 daemon.debug hostapd: wlan0: STA 40:a3:cc:a6:a2:25 WPA: received EAPOL-Key frame (4/4 Pairwise)
Fri Dec 20 06:59:16 2019 daemon.info hostapd: wlan0: STA 40:a3:cc:a6:a2:25 WPA: pairwise key handshake completed (RSN)

I cannot see any message about disconnection :frowning:
The logging starts when the client is connecting again.

Yeah, this is the problem. But there are no more logentrys about this issue. Maybe it is a clientproblem or RADIUS problem?

Is there anything suspicious in the radius logs?

I checked it long time ago, but there was nothing. I cant access the Logs right now :frowning: