@micampo then you are talking about the same issue. It is already addressed. The fix is in the next beta release. Coming soon.
Thank you!
Just upgraded to the full release 5.12 and DHCP failed on SM’s in router mode
I upgraded a dozen SMS from 5.12 rc33 to 5.12 final and it looks like all of them pulled dhcp fine. mine are all in router/nat mode.
Hello,
from 5.11.1 to 5.12 DHCP stop working. please fix!
hello,
we are using AC and N types in NAT mode with pppoe and from 5.11.1 to 5.12 DHCP stop working… next come back to 5.11.1 and all works fine. We have’t a test for AX types..
Are you experiencing this on N or AC SM’s? Are you using PPPoE?
Hello @netreality!
Could you please send me the tech support files for your AC and N subscribers via DM? I’d like to take a look at your configuration.
Also, could you confirm if you’ve observed this issue on AC subscribers as well, or if it’s strictly affecting the N radios?
Thank you!
Upgraded an ap today, all SM’s in router mode had DHCP failure.
I upgraded over 500 SM with no NAT issues on DHCP I know you said router mode You should try NAT and see if DHCP works.
Hello @wvvamike ,
could you please specify which subscribers are having the issue? N, AC or both?
I take it back I also notice DHCP this happen on a N radio and AC DHCP issues. I rebooted the AC and it started working as to the N I downgraded. This was on NAT mode.
All of our ePMP Force 180 units configured in NAT Mode stop assigning an IP address to the router connected behind the SM.
The behavior is consistent across multiple installations:
- SM model: Force 180
- Firmware: 5.12.0
- Operating mode: NAT
- WAN link is established correctly.
- The DHCP server on the SM no longer provides an IP address to the downstream router connected to the Ethernet port.
As a result, the customer router never receives a DHCP lease and remains without connectivity.
Rolling back to the previous firmware restores normal operation, so the issue appears to be specific to v5.12.0.
Hello @SKYNET360,
I don’t see the issue with AC subscribers. Could you PM me your techsupport file?
We are experiencing exactly the same thing, and we use the same NAT/PPPoE configuration.
Hello Community,
We’ve identified an issue where N-series radios fail to issue DHCP Offers on 5.12.0. This behavior occurs regardless of whether PPPoE is used.
Interestingly, we haven’t seen this issue on AC-series radios.
Could anyone confirm if they are experiencing this same DHCP behavior on Force 300 or Force 300 L models? Any techsupport from your setup would be greatly appreciated!
No issue with AC subscribers on my network.
Hello,
on elevated devices (UBNT) the same problem 5.12firmware=DHCP not working on lan port . Downgrading to 5.11.1=DHCP on lan port working
Hello @KrzysztofJ,
thank you for reporting this!
Elevated radios are N-series radios so are influenced by the defect too.
Today we updated several APs (with their subscribers) to version 5.12, and all of them started reporting DHCP issues. We’ve since downgraded to 5.11.1, which resolved the problem. We only saw this thread afterward. 