a week ago - last edited a week ago
So UMobile 1.3.0 with default config settings on AirGateway Installer 1.1.9 if WAN is set to DHCP and NAT is on with fall back address as default 192.168.1.1. and you try and connect to a PowerBeam M5-400 factory defaulted you can connect fine, now if you set the PowerBeam up as Static IP in bridge mode (Network cfg) to say 10.20.30.40 you can no longer connect to it even though it is in discovery. Now if you change the wan of the installer to the same subnet as the unit in discovery mode it logs in fine. So is NAT broken on the installer SW or is it a UMobile issue.
I think this is correct behavior. If WAN port on AGW Installer is on a different subnet than the Powerbeam, it can't connect to it. This scenario works only on new U-Installer which is able to add unknown subnets to U-Installer WAN port based on device discovery results.
U-Installer is a new product, it's now available only for beta testers - basically it's a successor of AGW Installer - it has own internal battery, USB 3 for charging, can feed more power to connected devices and has improved firmware so that you don't have to worry about IP address changes.