I configured a picostation as an access point and connected it to a port on a NS. This configuration allows a wifi connect laptop (posting this) to access the internet, but not mesh services. I can not connect to a MESH node using the node IP address or a qualified name.

So what is the best way to connect any computer toe the MESH via a WIFI interface. I think this is important for deployment at shelters or other locations.

73 de mike

I do this as a standard drop-box configuration. The tool I use is DD-WRT loaded on pretty much any router that it will load on; I've gathered many during my scavenging for WRT-54's. I've held demos with smartphones, tablets and various other wifi enabled stuff that audience members have brought.

To access all the mesh services, you need to set up the WIFI router as a 'DHCP forwarder' and connect it to any of the mesh node's ethernet ports. I haven't tried it with a Ubiquiti node yet, but this works well with Linksys. I usually strap two Linksys together, one running BBHN and the other running DD-WRT.

There's a couple of other tweaks that are documented on the DD-WRT Wiki, but basically the wifi router becomes passive and simply enables a wifi connection between standard wifi devices and the node. Note that because the node is providing DHCP services, you're limited to the 5 or 13 addresses that the node manages using this technique.

Incidentally, this is pretty much what you get when you attach a mesh node set up for 'AP' operation to a normal mesh node. I just don't like using mesh-capable hardware.

There are ways to bridge standard wifi into the mesh by connecting a wifi router to a node's LAN port(s) but it takes a fair bit of network configuration and tweaking. Look on this website for how to join a mesh to an existing LAN for details on that technique. For large events, this is the route you'd have to take.

I don't have them at hand, but if you need links to the related DD-WRT info, e-mail me offline and I can send the links.

It Can,

This is what the MESH_AP mode is.

However I personally would recommend using the routers original firmware admit better handles AP mode and provides other abilities. The MESH_AP mode is basically a very simple AP with limited configuration abilities for those times where your in the field, you need an AP now and it doesn't need to be fully features you just need to get it up and running.

Ideally your go kit should be designed with all this in mind and one shouldn't be hitting these sort of issues last minute in the field, but if it does happen  it is a way to get it to work.

Regarding two routers or wifi devices:

You will always want two as very few devices have ability to run on two different wifi channels at once (ones I've seen are dual band routers, usually in the 300+$ range)  and then you also want it to use a different antenna so you can point the signal locally (you don't want to send all the RF power away from you to the remote end of your link) I've seen evem less devices support this (1000$ + devices from enterprise router corporations building modular chassis)

Sounds like a configuration issue of some sorts. On the nanostation are you trying to use the main Ethernet port for internet and the secondary Ethernet port ofnthr NanoStation? If so we don't utilize this port and it won't route in to the mesh or respond to traffic.

The picostation is connected to the switch not directly to the NS5. The pico is configured:

wireless = access point

network = DHCP

pico has IP assigned by NS.

Win 8.1 laptop connects via pico and has access to internet via NS vlan but does not see NS IP directly

73 de mike

Ok the fact you can't get by IP address tells me it is not just a name issue so we can deal with that later.

my first thought is one of two scenarios 

1) Your not actually going through the mesh node because of a possible vlan configuration issue or similar.

Try a traceroute to 4.2.2.2 and verify the mesh node IP address shows up in the path.

2) I don't think this exists as an option but default the AirOS may be blocking path  because it's to a "non routeable" 10.0.0.0/8 range, if so disable that.

As a simple you may want to put the AirOS Picostation into bridge mode instead of routed mode as a quick test.

On a hunch, I tried the CHROME browser and it actually works. I have full access to the MESH nodes and services. Windows and internet  explorer has some setting screwed up.

regards

I deleted all IE files and then deleted them again. Exit and restart IE, It will not connect to localnode:8080.

The AP is using airmax set to AP/BRIDGE, Maybe there is a setting buried in the list blocking the connection?

Next thought.... I started IE and use http://localnode:8080 instead of just typing localnode:8080 as the URL... it worked. So without the http:// IE was kicking of the search setup.

mike