Q1) How can I allow access to port 2004 (olrsd_dot_draw) from the Wi-Fi (mesh) port? Presently, I can access the service from the LAN port, but not from "the mesh."  Curiously, in /etc/configure/olsrd I found

config LoadPlugin
  option library 'olsrd_dot_draw.so.0.3'
  option accept '127.0.0.1'
  option port '2003'

I tried changing "option accept" to 0.0.0.0, but no change. And then there is the port setting of 2003???

Q2) On the Rocket and NanoStation/NS Loco (I.e. MIMO radios), is there a way to see the receive information for the two chains separately?  I tried iwinfo, but it only shows the overall received Signal and Noise.  iw didn't do much better.

Looking at code: "iw dev wlan0 station dump"  the signal strength is in the brackets is each chain, otherwise it's a single chain connection.

I believe multiple chains will only apply if you get into the MCS Data rate for the connection, otherwise its a diversity receive and the strong of the two signals is reported regardless of which chain it came in on.

Majority of packets will be 1mbps single chain (required as you have to broadcast to support the slowest device, aka Linksys)  as they are intended for all devices to receive.

As for the mesh gateway inetd takes it from 2004 to 2003.  I will have to double check if the firewall rules permit it on WAN or not and if that was a design decision or bug if it doesn't (off hand I don't see a firewall rule in /etc/config/firewall to allow access on wan side) 

Your node should have the exact same data however.

Thanks for the information.  I had seen the signal strength data in brackets and thought it was some kind of high/low/avg - well, basically I didn't know what it was.  Now I do!

I agree, the topology should be the same on every node. But, it seems that if the net is not particularly resilient, some of the links do not propagate around the mesh.  Also, graphviz seems to like to place the local node at the top of the graph.  Sometimes it would be nice to change that -- even if only for political reasons ;-)  And... thanks for the clarity on the port numbering.  I see that now in the inetd config.

BTW, I tried adding the following to the firewall config, but no joy.

config rule
  option src 'wifi'
  option dest_port '2004'
  option proto 'tcp'
  option target 'ACCEPT'

Did you restart the firewall after editing ? (/etc/init.d/firewall restart&) 

But, of course ;-)

Hm, ok I'll have to look at it later on one of my nodes to see what is going on as I would think that would do it.