So I have an HP mini computer, running Win10 that my hAP absolutely refuses to assign an IP to it. The same computer will easily be assigned an IP by my internet router so I have to assume the DHCP client is working properly.
This is via a hardwired LAN connection and the hAP is set for 13 host direct so I know there are plenty of IPs in the pool available (only 5 are currently assigned).
I snooped around with SSH and couldn't find any relevant logs in /var/logs
You are here
hAP Lite doesn't like a Win10 box
Thu, 12/02/2021 - 19:35
#1
hAP Lite doesn't like a Win10 box
Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer
AH6LE, can you click on the link at the bottom of the Administration page, to download the support data file and attach back here?
What happens when turning on the LAN AP wifi option and connecting? Does this work?
Joe AE6XE
As for the Wifi, that's what I normally use to connect to the hAP. I haven't tried with the problem child computer but I will give it a try (it doesn't have native Wifi and I'll need to use a dongle)
Nothing is jumping out in the support data file. By testing the problem child computer on wifi may help to isolate the root cause -- is it in the DHCP protocol itself, or is it something unique with the devices' vlan or port settings, that we don't see over wifi.
[update: corrected lan interface]
If possible, run tcpdump on the node and the problem child computer to capture the packets on the LAN. Inspection of the handshaking may enlighten us to what is going on. On the node this is "tcpdump -i br-lan -w /tmp/lan.pcap -c 1000" -- will capture 1000 frames, should be during the time the laptop is trying to get an IP address. Not sure your familiarity with these command lines...
Joe AE6XE
tcpdump isn't installed:
root@AH6LE-HAP:~# cat /etc/os-release
NAME="AREDN"
VERSION="3.21.4.0"
ID="aredn"
ID_LIKE="lede openwrt"
PRETTY_NAME="AREDN 3.21.4.0"
VERSION_ID="3.21.4.0"
HOME_URL="https://openwrt.org/"
BUG_URL="https://bugs.openwrt.org/"
SUPPORT_URL="https://forum.openwrt.org/"
BUILD_ID="r11306-c4a6851c72"
OPENWRT_BOARD="ar71xx/mikrotik"
OPENWRT_ARCH="mips_24kc"
OPENWRT_TAINTS="no-all no-ipv6 mklibs busybox"
OPENWRT_DEVICE_MANUFACTURER="OpenWrt"
OPENWRT_DEVICE_MANUFACTURER_URL="https://openwrt.org/"
OPENWRT_DEVICE_PRODUCT="Generic"
OPENWRT_DEVICE_REVISION="v0"
OPENWRT_RELEASE="AREDN 3.21.4.0 r11306-c4a6851c72"
shot in the dark... edit /etc/config/dhcp and add "authoritarian 1", then reboot. Seems to be some issues, possibly timeout, with windows 10 and openwrt DHCP implementation. This may speed things up, although an issue if someone munges together the LANs of 2 nodes (which should be avoided anyway).
config dhcp
option interface 'lan'
option authoritative '1'
option start '218'
option limit '5'
option leasetime '1h'
option ignore '0'
list dhcp_option '121,10.0.0.0/8,10.216.52.217,172.16.0.0/12,10.216.52.217,0.0.0.0/0,10.216.52.217'
list dhcp_option '249,10.0.0.0/8,10.216.52.217,172.16.0.0/12,10.216.52.217,0.0.0.0/0,10.216.52.217'
Well this is a PITA...
Ran tcpdump and did a ipconfig /renew on the Win10 machine. Nothing reported until the Win10 computer timed out (Win10 reported unable to contact DHCP server). In other words, the lines regarding packets captured didn't appear until the timeout message was displayed
root@AH6LE-HAP:~# tcpdump -i br-lan -w /tmp/lan.pcap -c 1000
tcpdump: listening on br-lan, link-type EN10MB (Ethernet), capture size 262144 bytes
1000 packets captured
1007 packets received by filter
0 packets dropped
I'm going to try your option authoritative '1' idea next
And if I unplug from the hAP and plug it into my Cisco LAN router, it is assigned a functioning IP within seconds.....
All this time, I've been using Port 5 (the POE one). I was told it was on VLAN2 so it should be the same as Ports 2,3 and 4. Apparently this is wrong info.
I tried Port 3 and bingo.....
Sorry to waste your time and I appreciate your effort
Yep, wrong. Port 5 (VLAN 2) is exclusively used for DtD connections.
https://github.com/aredn/aredn
Joe AE6XE