Hi, I looked into this with Matt, so here's the update on the issue.
Matt had previously configured this radio as an SM in NAT mode which configures the radio with separate WAN and LAN IP addresses. When he switched it to an AP, there is only one IP address which is the bridge IP (WAN IP when in SM NAT mode). But when he switched the radio to Spectrum Analyzer mode from an AP, it used the SM's NAT configuration instead of remembering and using the APs bridge config. So from the LAN (Ethernet side), the radio was accessible through the LAN IP and local IP (169.254.1.1) but not the bridge (WAN) IP. Clearly we have to add some logic in there to remember what radio mode the device was previously in to prevent this from happening. One workaround for now is, before switching a radio to an AP from an SM, make sure the SM was configured for Bridge mode. This will avoid the situation until we provide a fix. Thank for exposing this bug, Matt! Sriram -----Original Message----- From: Af [mailto:af-boun...@afmug.com] On Behalf Of Matt Jenkins via Af Sent: Wednesday, October 08, 2014 11:06 AM To: af@afmug.com Subject: [AFMUG] ePMP on 2.2, run remote spectrum, can't get back in... Cambium, I am trying to run spectrum on an ePMP AP remotely. I changed the unit to Spectrum Analyzer and lost access. However I can ping the unit from the router on 169.254.1.1. So I got out another radio and set it up in the office and the same thing happened. It is accessible on 169.254.1.1 and 192.168.0.3, but not that IP it originally was configured with. The one on the tower is over an hour drive away. How do I get it back on it original IP so I can run spectrum remotely?
