Problem with DHCP server on SM in 5.12RC31

Products ePMP
1

@Fedor I need to report a potential issue with RC31 I have run into. Of the 14 SMs I upgraded last night I have had 2 of them contact about no internet. Looking into it both showed good signal and a 1G ethernet connection with no errors. SM in Router/NAT mode.

What I found is no DHCP leases or ARP entries for the customer’s router in the Monitor->Network tab. I had the customers reboot the routers and I rebooted the SM and no change. As a test I downgraded one SM back to 5.11.1 and after it came back online service was online again and I could see ARP and DHCP lease entry for their router.

I then grabbed a support file from the other SM and then downgraded. After the downgrade to 5.11.1 service was working again with ARP/DHCP lease for customer router.

I am going through each SM and so far I found 4 more that are doing the same. I cannot reach our managed wifi router (Aginet) but downgrading the SM to 5.11.1 fixes it.

So it looks like customers whose routers are set to pull DHCP from the SM are not working right. Customers who have routers from us but have a static IP on the router work fine. So it seems to be a problem with the DHCP server with SM in Router/NAT mode on 5.12RC31

2

Can confirm, we are almost exclusively NAT/Router mode with DHCP, and of the 26 radios I did on one AP as a first test, none had dhcp functioning. I was testing RC31 on my own connection, but of course, my radio is one of the only ones in bridge mode :man_facepalming:

(I moved my message here as this post got moved while I was typing lol)

3

After further checking I can confirm all 14SMs I upgraded from 5.11.1 to RC31 did not have DHCP working. Downgraded all to 5.11.1.

4

I can confirm that they’ve found the issues in RC31 (doesn’t seem to be a problem in earlier RC’s, like RC29). They’re working on a fix in an upcoming RC.

5

The issue with DHCP Server in 5.12.0-RC31 has been confirmed.
It has been introduced starting RC30.
We are working on the fix right now.
Thank you for reporting this!