Ok.  From "Using the Web Interface":

The other option in the WAN box is the Mesh Gateway. When a node has internet access from either the WAN or LAN, that access is available to the node itself and to any computer connected to the LAN port. When the Mesh Gateway is enabled, this node will advertise to the mesh that it has internet access and will act as a gateway and provide internet access to the rest of the mesh. By default it is disabled...

That would also allow for all the other computers in the mesh to have access to Internet, but he only wanted the master computer to have access, as I understood it.

Ok, so after digging through the Networking articles in the FAQ it seems that you want your computer to have only one network connection and it should go through a node.   

For instance you can connect your computer to a LAN port on the node, connect the WAN port of the node to your home network and disable any other network connections on your computer such as wireless. 

Well, this is basically a routing issue.

If you obtain DHCP from both networks you most certainly get default gateway also, from both networks. This information make up the routingtable in your computer and the tricky part is to route correct traffic to the correct network. In this situation DHCP is not the best solution and since you only have one computer that needs access to the internet I would propose that you assign it static IP on the nic facing the mesh and obtain DHCP from your network facing Internet.

This way you have a default route towards Internet to start with. Then you need to assign a static route on the computer pointing out the mesh network(s) via your closest mesh node.

Also make sure that you´re assigned, from the DHCP server, DNS settings such as your mesh node is primary and f.ex. google is secondary.

If you want, you could also let the DHCP server deliver the mesh routes, but you´ll have to configure the DHCP to obtain this result.

This might sound a bit clumsy, but it is the way to go if you run Windows on your computer. If you´d run Linux on your computer you could, theoretically, implement a vector routing protocol, found in the quagga package, to collect the routing information from your closest mesh node.

You might, however, as I just thought of, have some luck with the OLSR implementation for Windows, but I have not tried that myself.

I think this is a generic computer networking question - When you have one computer connected to two separate networks at once, how does the computer determine which one to use and how can you control it? 

I noticed this problem when setting up a node for the first time the other day.  When I was directly connected to a node I couldn't surf this website for the instructions I needed.  The computer was sending my http requests to the node instead of my internet connection. 

In a brief search, it looks like part of the solution may be to ensure that connection on the pc used for the node does not have a default gateway set.  I'm certain the experienced users here could give a definitive answer. 

Like this:
https://youtu.be/e3g8fGkzVbU?t=66
https://www.youtube.com/watch?v=N2aETw3CkZE

How can I get the cover off my WRT54G?  The antennas are removed from the back and two phillips head screws are removed from under the front rubber feet.

What else should I do to remove the cover?

Should I assume the mesh tunnel was / is not popular? No one has replied or posted here in a few years. Has this method been successful? Or is tunneling seem to be cheating?

Here is the fix for Linksys tunnel issues.  I've done a server and client and it fixed the connectivity issues.

http://www.broadband-hamnet.org/hsmm-mesh-forums/view-postlist/forum-5-problems-a-answers/topic-1527-vtun-tunneling.html

Kirk - N6SXR

I just received a Dell PowerConnect 6624 managed switch.  I'm trying to use it with a Bullet M2 mesh node running 3.1.0.  I see in the BBHN release notes for Ubiquiti that the switch should be configured so that Untagged = LAN and vlan1 = WAN, but I'm not sure that is possible with this switch.  Its manual states "VLAN 1 is the default VLAN of which all ports are members".  Apparently I can only configure vlans 2 - 4093.  Does that mean that this switch can't really be used with the current version of BBHN?

I tried connecting the mesh node to one of the switch's ports.  I connected a laptop to another of the switch's ports.  The mesh node is in 5 host direct mode.  The switch and the laptop were both assigned IP addresses by the mesh node.  From the laptop I can connect to the switch, the mesh node, and other nodes on the mesh.  From the mesh nodes I can ping the switch but I can't ping the laptop connected to the switch.  Is this due to my inability to configure vlan 1?  Is there any way around this using this switch?