I've been researching this issue and trying so many different solutions that I'm at the end of my rope.

Here's what I'm trying to do:

I have a UBNT Bullet M2 configured as a Mesh Node, NAT, and working properly, KG7OHT-001.

KG7OHT-001 is connected to LAN port 2 on KG7OHT-002, a WRT54G configured as a Mesh Access Point, NAT, SSID KG7OHT-WIFI.

KG7OHT-003-SERVER is connected via WIFI to SSID KG7OHT-WIFI.  It gets IP address 172.27.0.8.  It is running a webserver on port 80.

I can connect any WIFI device (laptop, phone, tablet) to KG7OHT-WIFI, get an IP address, and access http://KG7OHT-003-SERVER/.  Works great!

Next up: add another Mesh Node to the network.  This one is a Bullet M2 configured as a Mesh Node as KG7OHT-020.

If I connect a laptop to KG7OHT-020, I cannot get to http://KG7OHT-003-SERVER/.  Makes sense because it is on IP 172.27.0.8.  So to make that accessible from KG7OHT-020 (or any other Mesh Node on the network) I have to setup port forwarding on KG7OHT-001.

So I do that.  Under Port Forwarding I create a new rule on the WIFI interface, outside port 80, LAN IP 172.27.0.8 (KG7OHT-003-SERVER), LAN port 80, and click Add.  Then I save the config and 20 seconds later it's "ready."  Theoretically, I should now be able to connect from KG7OHT-020 to http://KG7OHT-001:80/ to access the web server that's running on KG7OHT-003-SERVER on IP 172.27.0.8.

However, the connection is never accepted.  It stalls for a bit but never establishes a connection to port 80.  I'm beginning to think that it's impossible to have a machine connected to localap and share its services to the outside mesh network.  Is this a bug, or did I configure something wrong?

Thanks so much in advance for your help!

KG7OHT
Chachi

Attached is a diagram of the network.  As discussed below, Laptop2 cannot connect to KG7OHT-003-SERVER through KG7OHT-001:80 with port forwarding configured as follows:

INTERFACE:OUTSIDE_PORT:LAN_IP:INSIDE_PORT
WIFI:80:KG7OHT-003-SERVER:80

However, Laptop1 can connect to KG7OHT-010-SERVER since KG7OHT-010-SERVER is wired through ethernet ports to KG7OHT-010.

Attachments
 meshnet diagram.jpg [77 KB]

SOLVED:

Boneheaded move on my part.  KG7OHT-001-SERVER has two network interfaces: en0, which was connected via cat5 to my home network and can get out to the Internet, and wlan0, which was connected to the mesh network via KG7OHT-002.

Once I disabled en0 (ifdown en0) I was able to hit KG7OHT-001-SERVER from anywhere in the mesh network.

So remember, boys and girls.  If you have two interfaces, set your mesh network as primary, or route all 10. traffic through that interface and all other traffic through your other interface.

73s!