Hi, after installing OpenWRT on my Xiaomi AC2350 router, both my tv-boxes can't connect to wi-fi. In system log it's stuck at DHCPDISCOVER DHCPOFFER without REQUEST. I use default setting. All other devices connect and work normally. Any suggestion?
A piece of system log:
Thu Aug 26 19:30:07 2021 daemon.info hostapd: wlan1: STA 08:da:35:df:c4:96 IEEE 802.11: disassociated
Thu Aug 26 19:30:07 2021 daemon.info hostapd: wlan1: STA 08:da:35:df:c4:96 IEEE 802.11: authenticated
Thu Aug 26 19:30:07 2021 daemon.info hostapd: wlan1: STA 08:da:35:df:c4:96 IEEE 802.11: associated (aid 1)
Thu Aug 26 19:30:07 2021 daemon.notice hostapd: wlan1: AP-STA-CONNECTED 08:da:35:df:c4:96
Thu Aug 26 19:30:07 2021 daemon.info hostapd: wlan1: STA 08:da:35:df:c4:96 WPA: pairwise key handshake completed (RSN)
Thu Aug 26 19:30:07 2021 daemon.notice hostapd: wlan1: EAPOL-4WAY-HS-COMPLETED 08:da:35:df:c4:96
Thu Aug 26 19:30:08 2021 daemon.info dnsmasq-dhcp[2811]: DHCPDISCOVER(br-lan) 08:da:35:df:c4:96
Thu Aug 26 19:30:08 2021 daemon.info dnsmasq-dhcp[2811]: DHCPOFFER(br-lan) 192.168.1.193 08:da:35:df:c4:96
Thu Aug 26 19:30:09 2021 daemon.info dnsmasq-dhcp[2811]: DHCPDISCOVER(br-lan) 08:da:35:df:c4:96
Thu Aug 26 19:30:09 2021 daemon.info dnsmasq-dhcp[2811]: DHCPOFFER(br-lan) 192.168.1.193 08:da:35:df:c4:96
Thu Aug 26 19:30:10 2021 daemon.info dnsmasq-dhcp[2811]: DHCPDISCOVER(br-lan) 08:da:35:df:c4:96
Thu Aug 26 19:30:10 2021 daemon.info dnsmasq-dhcp[2811]: DHCPOFFER(br-lan) 192.168.1.193 08:da:35:df:c4:96
Thu Aug 26 19:30:12 2021 daemon.info dnsmasq-dhcp[2811]: DHCPDISCOVER(br-lan) 08:da:35:df:c4:96
Thu Aug 26 19:30:12 2021 daemon.info dnsmasq-dhcp[2811]: DHCPOFFER(br-lan) 192.168.1.193 08:da:35:df:c4:96
Thu Aug 26 19:30:13 2021 daemon.info dnsmasq-dhcp[2811]: DHCPDISCOVER(br-lan) 08:da:35:df:c4:96
Thu Aug 26 19:30:13 2021 daemon.info dnsmasq-dhcp[2811]: DHCPOFFER(br-lan) 192.168.1.193 08:da:35:df:c4:96
It's 2 years later and I am facing the same issue here.
Interestingly, only for SOME devices on my network, other will go through DHCPDISCOVER, OFFER, DISCOVER with IP address and ACK.
The other devices go through DHCPDISCOVER/OFFER loop for multiple times (20-30x) before do either ACK or the device gives up...
Any hints how this got solved?
Given that the OP posted this so long ago, they probably were on a different version of OpenWrt relative to you (hopefully you're on something more recent).
That said, this is not a common problem. We need a lot more information to understand what might be causing this...
does this happen with both wired and wireless devices?
What specific devices are affected?
Do you run only a single router+AP, or do you have outboard APs and/or switches? And if so, what firmware do they use and how are they configured?
Any other relevant info?
Configs?
Please copy the output of the following commands and post it here using the "Preformatted text </> " button:
Remember to redact passwords, MAC addresses and any public IP addresses you may have:
so far, I've only noticed this on wireless devices
I am running 22.03 version on x86 HW with 4x intel 2.5Gb ports, one setup as WAN, another as LAN with 7 vlans
the APs are EAP670
the connecting client is Samsung Galaxy tab S6 lite, tested with both open-source e.foundation OS and the stock firmware
the router and AP are connected using Zyxel GS1900-24HP, which supports VLANs and the ports for both the AP and the router are marked as trunk, all VLANs are allowed to flow through
Observed situation:
if the device was connected with different IP (e.g. connected to WiFi network linked to different VLAN), the REQUEST/OFFER loop does not happen, the device will get IP on the first try
if the device was connected to the main VLAN/WiFi combo and disconnects, on next reconnect it will go through ~1 minute of REQUEST/OFFER loop, until it connects
any other devices (e.g. Xiaomi redmi 8T with e.foundation OS or redmi 10 with stock firmware) connect no problem, so do all my Shelly devices.
I specifically created a VLAN/WiFi combo for only 5GHz network and another for 2.4GHz network - the behavior is always the same.
If I set the "use randomize MAC" on the android device, the behavior is the same as if I use the HW MAC, just getting different IP address.
Here is the log from last few minutes:
Aug 9 23:11:13 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) 86:3c:80:ef:1b:7b
Aug 9 23:11:13 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.108 86:3c:80:ef:1b:7b
Aug 9 23:11:13 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) 86:3c:80:ef:1b:7b
Aug 9 23:11:13 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.108 86:3c:80:ef:1b:7b
Aug 9 23:11:14 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) 86:3c:80:ef:1b:7b
Aug 9 23:11:14 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.108 86:3c:80:ef:1b:7b
Aug 9 23:11:17 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) 86:3c:80:ef:1b:7b
Aug 9 23:11:17 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.108 86:3c:80:ef:1b:7b
Aug 9 23:11:17 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) 86:3c:80:ef:1b:7b
Aug 9 23:11:17 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.108 86:3c:80:ef:1b:7b
Aug 9 23:11:18 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) 86:3c:80:ef:1b:7b
Aug 9 23:11:18 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.108 86:3c:80:ef:1b:7b
Aug 9 23:11:19 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) 86:3c:80:ef:1b:7b
Aug 9 23:11:19 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.108 86:3c:80:ef:1b:7b
Aug 9 23:11:20 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) 86:3c:80:ef:1b:7b
Aug 9 23:11:20 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.108 86:3c:80:ef:1b:7b
Aug 9 23:11:20 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) 86:3c:80:ef:1b:7b
Aug 9 23:11:20 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.108 86:3c:80:ef:1b:7b
Aug 9 23:11:20 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) 86:3c:80:ef:1b:7b
Aug 9 23:11:20 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.108 86:3c:80:ef:1b:7b
Aug 9 23:11:21 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) 86:3c:80:ef:1b:7b
Aug 9 23:11:21 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.108 86:3c:80:ef:1b:7b
Aug 9 23:11:23 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) 86:3c:80:ef:1b:7b
Aug 9 23:11:23 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.108 86:3c:80:ef:1b:7b
Aug 9 23:11:24 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) 86:3c:80:ef:1b:7b
Aug 9 23:11:24 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.108 86:3c:80:ef:1b:7b
Aug 9 23:11:25 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) 86:3c:80:ef:1b:7b
Aug 9 23:11:25 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.108 86:3c:80:ef:1b:7b
Aug 9 23:11:26 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) 86:3c:80:ef:1b:7b
Aug 9 23:11:26 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.108 86:3c:80:ef:1b:7b
Aug 9 23:11:31 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) 86:3c:80:ef:1b:7b
Aug 9 23:11:31 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.108 86:3c:80:ef:1b:7b
Aug 9 23:11:33 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) 86:3c:80:ef:1b:7b
Aug 9 23:11:33 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.108 86:3c:80:ef:1b:7b
Aug 9 23:11:33 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) 86:3c:80:ef:1b:7b
Aug 9 23:11:33 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.108 86:3c:80:ef:1b:7b
Aug 9 23:11:34 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) 86:3c:80:ef:1b:7b
Aug 9 23:11:34 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.108 86:3c:80:ef:1b:7b
Aug 9 23:11:37 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) 86:3c:80:ef:1b:7b
Aug 9 23:11:37 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.108 86:3c:80:ef:1b:7b
Aug 9 23:11:38 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) 86:3c:80:ef:1b:7b
Aug 9 23:11:38 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.108 86:3c:80:ef:1b:7b
Aug 9 23:11:38 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) 86:3c:80:ef:1b:7b
Aug 9 23:11:38 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.108 86:3c:80:ef:1b:7b
Aug 9 23:11:39 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) 86:3c:80:ef:1b:7b
Aug 9 23:11:39 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.108 86:3c:80:ef:1b:7b
Aug 9 23:11:40 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) 86:3c:80:ef:1b:7b
Aug 9 23:11:40 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.108 86:3c:80:ef:1b:7b
Aug 9 23:11:40 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) 86:3c:80:ef:1b:7b
Aug 9 23:11:40 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.108 86:3c:80:ef:1b:7b
Aug 9 23:11:41 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) 86:3c:80:ef:1b:7b
Aug 9 23:11:41 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.108 86:3c:80:ef:1b:7b
Aug 9 23:11:42 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) 86:3c:80:ef:1b:7b
Aug 9 23:11:42 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.108 86:3c:80:ef:1b:7b
Aug 9 23:11:44 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) 86:3c:80:ef:1b:7b
Aug 9 23:11:44 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.108 86:3c:80:ef:1b:7b
Aug 9 23:11:44 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) 86:3c:80:ef:1b:7b
Aug 9 23:11:44 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.108 86:3c:80:ef:1b:7b
Aug 9 23:11:45 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) 86:3c:80:ef:1b:7b
Aug 9 23:11:45 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.108 86:3c:80:ef:1b:7b
Aug 9 23:11:46 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) 86:3c:80:ef:1b:7b
Aug 9 23:11:46 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.108 86:3c:80:ef:1b:7b
Aug 9 23:11:48 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) 86:3c:80:ef:1b:7b
Aug 9 23:11:48 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.108 86:3c:80:ef:1b:7b
Aug 9 23:11:52 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) 86:3c:80:ef:1b:7b
Aug 9 23:11:52 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.108 86:3c:80:ef:1b:7b
Aug 9 23:11:53 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) 86:3c:80:ef:1b:7b
Aug 9 23:11:53 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.108 86:3c:80:ef:1b:7b
Aug 9 23:11:54 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) 86:3c:80:ef:1b:7b
Aug 9 23:11:54 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.108 86:3c:80:ef:1b:7b
Aug 9 23:12:26 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) 86:3c:80:ef:1b:7b
Aug 9 23:12:26 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.108 86:3c:80:ef:1b:7b
Aug 9 23:12:26 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) 86:3c:80:ef:1b:7b
Aug 9 23:12:26 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.108 86:3c:80:ef:1b:7b
Aug 9 23:12:26 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) 86:3c:80:ef:1b:7b
Aug 9 23:12:26 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.108 86:3c:80:ef:1b:7b
Aug 9 23:12:26 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) 86:3c:80:ef:1b:7b
Aug 9 23:12:26 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.108 86:3c:80:ef:1b:7b
Aug 9 23:12:26 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) 86:3c:80:ef:1b:7b
Aug 9 23:12:26 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.108 86:3c:80:ef:1b:7b
Aug 9 23:12:26 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) 86:3c:80:ef:1b:7b
Aug 9 23:12:26 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.108 86:3c:80:ef:1b:7b
Aug 9 23:12:27 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) 86:3c:80:ef:1b:7b
Aug 9 23:12:27 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.108 86:3c:80:ef:1b:7b
Aug 9 23:12:27 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) 86:3c:80:ef:1b:7b
Aug 9 23:12:27 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.108 86:3c:80:ef:1b:7b
Aug 9 23:12:29 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) 86:3c:80:ef:1b:7b
Aug 9 23:12:29 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.108 86:3c:80:ef:1b:7b
Aug 9 23:12:29 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) 86:3c:80:ef:1b:7b
Aug 9 23:12:29 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.108 86:3c:80:ef:1b:7b
Aug 9 23:12:30 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) 86:3c:80:ef:1b:7b
Aug 9 23:12:30 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.108 86:3c:80:ef:1b:7b
Aug 9 23:12:31 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) 86:3c:80:ef:1b:7b
Aug 9 23:12:31 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.108 86:3c:80:ef:1b:7b
Aug 9 23:12:33 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) 86:3c:80:ef:1b:7b
Aug 9 23:12:33 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.108 86:3c:80:ef:1b:7b
Aug 9 23:12:37 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) 86:3c:80:ef:1b:7b
Aug 9 23:12:37 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.108 86:3c:80:ef:1b:7b
Aug 9 23:12:37 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) 86:3c:80:ef:1b:7b
Aug 9 23:12:37 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.108 86:3c:80:ef:1b:7b
Aug 9 23:12:38 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) 86:3c:80:ef:1b:7b
Aug 9 23:12:38 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.108 86:3c:80:ef:1b:7b
Aug 9 23:12:40 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) 86:3c:80:ef:1b:7b
Aug 9 23:12:40 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.108 86:3c:80:ef:1b:7b
Aug 9 23:13:52 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) 86:3c:80:ef:1b:7b
Aug 9 23:13:52 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.108 86:3c:80:ef:1b:7b
Aug 9 23:13:52 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) 86:3c:80:ef:1b:7b
Aug 9 23:13:52 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.108 86:3c:80:ef:1b:7b
Aug 9 23:13:52 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) 86:3c:80:ef:1b:7b
Aug 9 23:13:52 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.108 86:3c:80:ef:1b:7b
Aug 9 23:13:52 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) 86:3c:80:ef:1b:7b
Aug 9 23:13:52 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.108 86:3c:80:ef:1b:7b
Aug 9 23:13:52 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) 86:3c:80:ef:1b:7b
Aug 9 23:13:52 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.108 86:3c:80:ef:1b:7b
Aug 9 23:13:52 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) 86:3c:80:ef:1b:7b
Aug 9 23:13:52 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.108 86:3c:80:ef:1b:7b
Aug 9 23:13:52 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) 86:3c:80:ef:1b:7b
Aug 9 23:13:52 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.108 86:3c:80:ef:1b:7b
Aug 9 23:13:53 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) 86:3c:80:ef:1b:7b
Aug 9 23:13:53 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.108 86:3c:80:ef:1b:7b
Aug 9 23:13:55 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) 86:3c:80:ef:1b:7b
Aug 9 23:13:55 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.108 86:3c:80:ef:1b:7b
Aug 9 23:13:55 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) 86:3c:80:ef:1b:7b
Aug 9 23:13:55 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.108 86:3c:80:ef:1b:7b
Aug 9 23:13:56 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) 86:3c:80:ef:1b:7b
Aug 9 23:13:56 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.108 86:3c:80:ef:1b:7b
Aug 9 23:13:57 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) 86:3c:80:ef:1b:7b
Aug 9 23:13:57 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.108 86:3c:80:ef:1b:7b
Aug 9 23:13:59 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) 86:3c:80:ef:1b:7b
Aug 9 23:13:59 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.108 86:3c:80:ef:1b:7b
Aug 9 23:14:04 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) 86:3c:80:ef:1b:7b
Aug 9 23:14:04 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.108 86:3c:80:ef:1b:7b
Aug 9 23:14:04 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) 86:3c:80:ef:1b:7b
Aug 9 23:14:04 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.108 86:3c:80:ef:1b:7b
Aug 9 23:14:05 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) 86:3c:80:ef:1b:7b
Aug 9 23:14:05 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.108 86:3c:80:ef:1b:7b
Aug 9 23:14:06 router dnsmasq-dhcp[1]: DHCPREQUEST(eth0.10) 10.10.10.108 86:3c:80:ef:1b:7b
Aug 9 23:14:06 router dnsmasq-dhcp[1]: DHCPACK(eth0.10) 10.10.10.108 86:3c:80:ef:1b:7b sanchoTablet
This could be the problem here... bridging eth0 and eth0.1 is not recommended. If the network should be tagged on the port, remove eth0. If the network is expected to be untagged, remove eth0.1.
Thanks for the tip.
I did not realized it.
Unfortunately, it did not helped.
Removed the bridge interface altogether and linked the LAN interface directly to eth0.1.
Rebooted the router fully, tried to reconnect and the same problem...
Aug 9 23:49:42 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) a8:30:bc:ec:8d:07
Aug 9 23:49:42 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.63 a8:30:bc:ec:8d:07
Aug 9 23:49:42 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) a8:30:bc:ec:8d:07
Aug 9 23:49:42 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.63 a8:30:bc:ec:8d:07
Aug 9 23:49:43 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) a8:30:bc:ec:8d:07
Aug 9 23:49:43 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.63 a8:30:bc:ec:8d:07
Aug 9 23:49:43 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) a8:30:bc:ec:8d:07
Aug 9 23:49:43 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.63 a8:30:bc:ec:8d:07
Aug 9 23:49:44 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) a8:30:bc:ec:8d:07
Aug 9 23:49:44 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.63 a8:30:bc:ec:8d:07
Aug 9 23:49:45 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) a8:30:bc:ec:8d:07
Aug 9 23:49:45 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.63 a8:30:bc:ec:8d:07
Aug 9 23:49:45 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) a8:30:bc:ec:8d:07
Aug 9 23:49:45 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.63 a8:30:bc:ec:8d:07
Aug 9 23:49:46 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) a8:30:bc:ec:8d:07
Aug 9 23:49:46 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.63 a8:30:bc:ec:8d:07
Aug 9 23:49:48 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) a8:30:bc:ec:8d:07
Aug 9 23:49:48 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.63 a8:30:bc:ec:8d:07
Aug 9 23:49:49 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) a8:30:bc:ec:8d:07
Aug 9 23:49:49 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.63 a8:30:bc:ec:8d:07
Aug 9 23:49:50 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) a8:30:bc:ec:8d:07
Aug 9 23:49:50 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.63 a8:30:bc:ec:8d:07
Aug 9 23:49:50 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) a8:30:bc:ec:8d:07
Aug 9 23:49:50 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.63 a8:30:bc:ec:8d:07
Aug 9 23:49:52 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) a8:30:bc:ec:8d:07
Aug 9 23:49:52 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.63 a8:30:bc:ec:8d:07
Aug 9 23:49:57 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) a8:30:bc:ec:8d:07
Aug 9 23:49:57 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.63 a8:30:bc:ec:8d:07
Aug 9 23:49:57 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) a8:30:bc:ec:8d:07
Aug 9 23:49:57 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.63 a8:30:bc:ec:8d:07
Aug 9 23:49:58 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) a8:30:bc:ec:8d:07
Aug 9 23:49:58 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.63 a8:30:bc:ec:8d:07
Aug 9 23:50:01 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) a8:30:bc:ec:8d:07
Aug 9 23:50:01 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.63 a8:30:bc:ec:8d:07
Aug 9 23:50:01 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) a8:30:bc:ec:8d:07
Aug 9 23:50:01 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.63 a8:30:bc:ec:8d:07
Aug 9 23:50:02 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) a8:30:bc:ec:8d:07
Aug 9 23:50:02 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.63 a8:30:bc:ec:8d:07
Aug 9 23:50:02 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) a8:30:bc:ec:8d:07
Aug 9 23:50:02 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.63 a8:30:bc:ec:8d:07
Aug 9 23:50:03 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) a8:30:bc:ec:8d:07
Aug 9 23:50:03 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.63 a8:30:bc:ec:8d:07
Aug 9 23:50:04 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) a8:30:bc:ec:8d:07
Aug 9 23:50:04 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.63 a8:30:bc:ec:8d:07
Aug 9 23:50:04 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) a8:30:bc:ec:8d:07
Aug 9 23:50:04 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.63 a8:30:bc:ec:8d:07
Aug 9 23:50:05 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) a8:30:bc:ec:8d:07
Aug 9 23:50:05 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.63 a8:30:bc:ec:8d:07
Aug 9 23:50:07 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) a8:30:bc:ec:8d:07
Aug 9 23:50:07 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.63 a8:30:bc:ec:8d:07
Aug 9 23:50:08 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) a8:30:bc:ec:8d:07
Aug 9 23:50:08 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.63 a8:30:bc:ec:8d:07
Aug 9 23:50:09 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) a8:30:bc:ec:8d:07
Aug 9 23:50:09 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.63 a8:30:bc:ec:8d:07
Aug 9 23:50:10 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) a8:30:bc:ec:8d:07
Aug 9 23:50:10 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.63 a8:30:bc:ec:8d:07
Aug 9 23:50:12 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) a8:30:bc:ec:8d:07
Aug 9 23:50:12 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.63 a8:30:bc:ec:8d:07
Aug 9 23:50:17 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) a8:30:bc:ec:8d:07
Aug 9 23:50:17 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.63 a8:30:bc:ec:8d:07
Aug 9 23:50:17 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) a8:30:bc:ec:8d:07
Aug 9 23:50:17 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.63 a8:30:bc:ec:8d:07
Aug 9 23:50:18 router dnsmasq-dhcp[1]: DHCPDISCOVER(eth0.10) a8:30:bc:ec:8d:07
Aug 9 23:50:18 router dnsmasq-dhcp[1]: DHCPOFFER(eth0.10) 10.10.10.63 a8:30:bc:ec:8d:07
Aug 9 23:50:18 router dnsmasq-dhcp[1]: DHCPREQUEST(eth0.10) 10.10.10.63 a8:30:bc:ec:8d:07
Aug 9 23:50:18 router dnsmasq-dhcp[1]: DHCPACK(eth0.10) 10.10.10.63 a8:30:bc:ec:8d:07 sanchoTablet
Given that this is a DHCP issue we're trying to debug, it'll be necessary to see these files to make sure there isn't an obvious problem in one or both. You can remove DHCP reservations and other sensitive data (just make it clear that you have redacted that info).
Also, it is entirely possible that there is something with the OS on the phone given that it is the only one having the issue.
I don't think it is truly necessary, but consider adding this to your mainNet DHCP server:
option dhcpv4 'server'
There are two MAC addrsses here... try removing one and setting just one.
Also, make sure that the device is always presenting the same MAC... this would mean turning off MAC randomization/privacy if it enabled on that device.
The behavior seems the same.
Even when selecting random MAC on the device and after few minutes (!!!) receiving a non-allocated IP address from DHCP pool, not from the allocated one.
I want to point out that a lot of devices work OK, just some do have this connectivity issue - Samsung tablets, Microsoft surface devices and one old cellphone (OnePlus one).
The rest gets IP after first attempt.
So I do start to lean towards the problem on the client side...
One other thing -- it is possible that the APs are swallowing some of the DHCP packets. This was a known issue on Unifi APs (stock firmware 4.3.21+; I still run 4.3.20 years later for this reason, although I am thinking of trying an upgrade).
I did a test - limited one WiFi to a specific AP and tried to connect to that one - same result.
I will now try to connect using ethernet cable on the tablet (not sure it will work) to see if the DHCP problem remains...
Well, there is some interesting development.
I've dug out my old Unifi AP (U6-Pro) and installed it into garage.
I've set up the same VLAN/WiFi combination (just modified the AP SSID, so I know where I connect).
I connected to it using the same Samsung tablet and got DHCP in 2 seconds.
So I disconnected, connected back to the old WiFi and got the IP in 2 seconds, too.
Tried to reboot the tablet, disconnect and reconnect to the old WiFi, now everything works super-fast.
What I think is the problem here - I have 3x EAP670 in my house. All of them transmit the same SSIDs, on different channels and on 2 different frequencies (2.4 and 5GHz).
As the tablet is connecting, it might (due to some roaming or something) transmit the DHCP using multiple APs. As these arrive in different order to the OpenWRT, it responds in sequence - this sequence then MIGHT confuse the device and fail to actually finish the DHCP sequence.
Next step - I will try to isolate the device to a specific AP, but now I cannot reproduce the problem anymore
No, it doesn't work like that. The client will connect to exactly one AP at a time. It could be an issue with the configuratoin of one or two of the APs, though, such that the client is unable to properly obtain an IP through it.