After several days of fully functional AP, the communication from wireless part to LAN seems partially broken.
RT-N56U (10.11.13.10) is connected to existing
lan10.11.13.0/24 (WAN port not used)
It provides 2 WLAN networks on 2.4 GHz radio:
wlan0extends the LAN, i.e. DHCP server is provided by router 10.11.13.1, and
wlan0-1creates a separate network (10.11.17.0/24) for guests, where DHCP is provided by RT-N56U.
This is a fully functional setup.
After several days (and occassionally even sooner):
wlan0clients cannot get IP address. RT-N56U ('wifi') does not show anything suspicious and the 'router' (10.11.13.1) logs DHCP offer failure:
Feb 11 18:43:01 tiger rsyslogd: Feb 11 18:43:01 wifi hostapd: wlan0: STA 4c:66:41:94:a2:c5 IEEE 802.11: associated (aid 2) Feb 11 18:43:01 tiger rsyslogd: Feb 11 18:43:01 wifi hostapd: wlan0: AP-STA-CONNECTED 4c:66:41:94:a2:c5 Feb 11 18:43:01 tiger rsyslogd: Feb 11 18:43:01 wifi hostapd: wlan0: STA 4c:66:41:94:a2:c5 WPA: pairwise key handshake completed (RSN) Feb 11 18:43:02 tiger rsyslogd: Feb 11 18:43:02 router router: dhcp1 offering lease 10.11.13.140 for 4C:66:41:94:A2:C5 without success
wlan0-1clients get IP address correctly (thanks to DHCP served by RT-N56U), but cannot access internet (i.e. not even the 'router').
It appears as if the communication from wireless clients to
lan gets partially broken.
However, I can still fully connect to luci on the
lan port (i.e. wired connection).
I tried (step by step) to:
- restart wireless radio0;
- restart network (System // Startup // Network), dnsmasq, firewall, odhcpd;
but without any affect on the above behaviour. Rebooting RT-N56U solves the problem, though.
Any ideas what might be the culprit and how to debug that? So far, it helps to reboot the device overnight via cron, but that does not help always...