ePMP NAT mode?

I know vendors have differences in operations, but I cannot seem to get the ePMP to mimic how I have my network setup on my CPEs (SMs).

On my Ubiquiti CPEs I have the Wireless (WAN) set to DHCP with a fallback of 192.168.1.20. If the CPE is not connected to an AP or fails get an IP from the network then its wireless IP is 192.168.1.20.
I also have the CPE in Router/NAT mode with the LAN IP as 192.168.99.1 and the DHCP pool of 192.168.99.100-192.168.99.110.

What happens then is if the CPE is not connected to an AP I can still get a DHCP address from the LAN port of the CPE in the 192.168.99.x subnet or I can manually set my PC to an IP in the 192.168.99.x subnet and manage the CPE via 192.168.99.1.

However, I tried to do the same in the ePMP 4525 CPE and I cannot get an IP address at all. If I set my PC to 168.254.1.230 I can now ping 192.168.99.1 or manage the CPE via 169.254.1.1. If I set my PC to 192.168.99.230 I can manage the IP on 192.168.99.1 but the SM will not give my PC a DHCP address.

What am I missing to duplicate the Ubiquiti settings and have it operate pretty much the same?

Here are my Ubnt settings followed by my ePMP settings.




Here is another view of the 4525 configuration. I can reach the SM using the 169.254.1.1 or 192.168.99.1 address if I manually set my PC to IPs in those subnets, but when I set my PC to DHCP I fail to get an IP.

Is NAT DHCP broken in these new SMs?

What firmware are you running?

1 Like

The firmware it came with. 5.4

Please try updating to 5.4.1-RC10 and see if you still have issues with NAT and DHCP.

2 Likes

5.4.1RC10 FW fixed it and now DHCP is working in NAT mode.

3 Likes

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.