Possible Bugs

I just upgraded my Bullet M2 with 3.19.3.0. Using Internet Explorer, the activity wheel just spins endlessly. The chart feature works flawlessly when I use Firefox. IE is often needed for our mesh for the occasional ActiveX plug-in we use.
Addendum: I just duplicated this problem on a Nano Station M2, and with a different computer also using the IE browser.

Over the last several days, I have been udating a number of nodes to 3.19.3.0, mostly AirRouters running tunnels. A few months ago, I reconfigured these nodes with new, static, WAN addresses.

Version 3.19.3.0 on a Rocket M5
This is a new installation with one link.  I installed MeshChat on the node itself and although it shows up in Mesh Status display:


It does not show up on the Services page:


until I add a dummy port forward entry:

Has anyone around experienced any issues with PowerBeam M5's (in our case the 400's) and 3.19.3.0 where after a period of time, they go offline for no apparently reason? 

The one time we were able to get onto a unit after it went down via a dtdlink and using an IP address that was a bridge from the dtd device, any command ran via ssh resulted in an out of memory error.

If you don't catch it right away, you have to power cycle it to come back online.

First a little background.  From my house there is not an AREDN path to anything.  My only connection from home is a tunnel to a node at my office which in turn has a great RF path to the local network.  At home I have a Mikrotik RB952Ui-5ac2nD (hAP ac Lite) that provides me local AREDN access to the network via the tunnel.  To keep the story short, I have discovered that if there is a LAN connection between port 5 of the hAP (the DtD port) and the switch, then the LAN connection is dropping A LOT of packets - about 40% of pings fail.  This is 100% repeatable.  Originally I determined what

Hi Folks!
Love the new RouterBoard implementation, but there may be some fixes needed.
I brought it up with the 2 GHz mesh node and 5 GHz AP running.
worked fine, except that the node would only show its IP address in the mesh status of its neighbor and was not shown anywhere else, which makes sense for a node with no name to share.
Then I changed it to have the mesh node off and went to a 2GHz AP.

Installing nightly build 165 on a Nanostation M3 with AirOS (new out of the box, but I've had it for at least a year).
All went well until I tried to configure it.  Set hostname, password and distance setting  Tried to save the configuration but it errored out with
"Configuration NOT saved!
Invalid Mesh IP address"

Can someone describe a method I can use to verify that the forward that I am creating in the web interface is making it to the 'guts' of the node?

Is there some command line foo that I can use to check it?  I am going to keep digging, but if you know off hand that would help.

Matt