EAP 225 firmware 2.6.0 issue with DHCP ACK
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
I upgraded from 2.4.0 to 2.6.0 on the EAP via omada controller on linux.
After the upgrade, several clients connecting to the EAP 225 on the omada controller would only show IP addresses of 255.255.255.255.
Other clients connecting to the 3 x EAP245s had no issues.
I then checked the DHCP server, and it was receiving loads of DHCP DISCOVER and DHCP OFFERS, but no DHCP ACK
I then downgraded back to 2.4.0 and all the issues went away.
Anyone else had issues with that?
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Waga wrote
I then checked the DHCP server, and it was receiving loads of DHCP DISCOVER and DHCP OFFERS, but no DHCP ACK
I then downgraded back to 2.4.0 and all the issues went away.
Anyone else had issues with that?
No problems here with several sites. But note that the new firmware fixed a problem with untagged/tagged frames. Are you using multi-SSIDs with VLAN and a default VLAN?
Could it be that DHCPOFFERS from the DHCP server are not answered with DHCPREQUESTS from clients?
- Copy Link
- Report Inappropriate Content
@R1D2 yes to all (multi-vlan w/default and multi-ssid)
It could be that the DHCP OFFERS are responded to , but the clients not responding.
Thanks for the input! Looks like the situation with me is that the powerline adapter I am using is the culprit (tagged vlan traffic being dropped) back to a managed switch.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
@shberge I was just about to do that!
- Copy Link
- Report Inappropriate Content
Waga wrote
yes to all (multi-vlan w/default and multi-ssid)
The EAP firmware bug fix is for untagged frames (default VLAN!), which have been errorneously sent to VLAN-tagged SSIDs before.
So if you exchange the switch by a managed one, ensure that every SSID using VLANs can pass DHCPOFFERS from the DHCP server to the clients.
Personally, I don't mix tagged and untagged traffic, but this is just our policy here, not justified by technical reason. Anyway, each separate VLAN needs access to the DHCP server, either by separate server instances in each VLAN or by using a DHCP relay.
- Copy Link
- Report Inappropriate Content
@R1D2 Yeah I know. I don't generally mix them at work, but this is at home.
I didn't twig that the EoP adapters were non 8021qs. I do have managed (5 x HP procurves 2810s etc) which are obv all 802.1q, but just the devolos aren't
Anyway, thanks for the dbugging assist.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 1386
Replies: 6
Voters 0
No one has voted for it yet.