06-17-2017 12:46 PM - edited 06-17-2017 12:54 PM
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.
06-18-2017 11:15 AM
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.
06-18-2017 02:34 PM
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.
07-17-2017 03:45 PM - edited 07-17-2017 03:50 PM
Yep, I'm in the same boat, although I only have one AGI. I can configure the AirGateway Installer to use an IP on the same subnet as the radio and access the radio, but then the Installer is "not configured correctly" according to U-Mobile. If U-Mobile would detect the subnet mismatch and ask me for an IP and subnet to use, It could then apply that IP as an alias of the WAN port to gain access. In my case, I would like it to cache my responses for future use. It would be even better if it could detect that the IP of the radio is within a cached subnet and enter that ip and subnet as the default when it askes.
It's not rocket science. Aside from the caching, it's only a little above script kitty level work.