Hi.

how do i share my private internet connection over the HSMM net? 

to make it "simple" and have all system in one place. I would like to have internet access at my repeater tower. to connect  aprs,echolink and d-star ++ so my idea is to use the HSMM system to wireless send my private internet connection to my repeater QTH

So i have one linksys router at home connected to my ISP router, and i have a connection to my other HSMM linksys router at my repeater location.

they are talking to each other. but can't get the internet connection i need. 

is there a special thing i have to do. to make this work. 

Anybody going to be at the Orlando Hamfest this year? I'll be there and will have my mobile node running as I always do.

Eric...KD4MZM...

Not technically possible, no matter what you try (connecting v2 and v3 nodes by any method). v2 used the OLSRD 'secure' handshake to talk only with a compatible node (v2 ignores packets unless they have the correct signature).

v3 does NOT use the OLSRD-secure functionality. OLSRD-Secure is a desired feature based on a secret key to authorize a node to connect--a default key is packaged in the v2 images (version 1.1.x releases of the bbhn images). We found, submitted, and fixed a couple of showstopper bugs before deciding it was in our best interest to pull olsrd-secure out (one of the factors to create v3).

We learned that olsrd-secure was not sufficiently stable and had been abandoned by the olsr.org community. WE will have to take ownership and make it usable-stable should we decide to do so.

It is in everyone's best interest to upgrade to v3 (version 3.0.x of the bbhn images) without delay.

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.

In the best of all possible worlds, everyone always uses the latest version of the firmware, but in a recent emcomm exercise, we realized that in the "real world" you bring what you have, and about half of the nodes that were brought to the exercise were v2 and half were v3.  In most cases, the owners just didn't get around to reflashing their nodes, but there might be some nodes that are high up on a tower or otherwise in a remote location where it is difficult to upgrade them to the latest firmware in a timely manner. 

I understand that a v2 mesh cannot connect to a v3 mesh over the air.  I tried to link the meshes via ethernet.  Here's what I have already tried (unsuccessfully):

1.  I tried connecting the WAN port of a v2 Linksys router to the LAN port of a v3 Linksys router.  The v2 router was configured as a "mesh gateway".  The v3 router was configured as a normal mesh node.  When I opened the mesh status page on the v2 mesh node, I only saw the v2 mesh nodes.  When I opened the mesh status page on the v3 mesh node, the ip addresses of the v2 nodes wifi interfaces appeared on the "current neighbors", but I could not connect to any of them.  None of the ethernet interfaces of the v2 nodes appeared on the "current neighbors" list.

2.  I configured a Netgear GS105E switch in accordance with the instructions published by AE5CA, at  http://ae5ca.com/?p=49.   I connected a Ubiquiti Nanostation NSM2 v2 node to VLAN 1, 2 and 10.  I connected a Ubiquiti Bullet M2 v3 node to VLAN 1, 2, and 20.  I tried various combinations of mesh gateway and mesh node settings. The results were similar to the test with the Linksys routers.  When I opened the mesh status page on the v2 mesh node, I only saw the v2 mesh nodes.  When I opened the mesh status page on the v3 mesh node, the ip addresses of the v2 nodes wifi interfaces appeared on the "current neighbors", but I could not connect to any of them.  None of the ethernet interfaces of the v2 nodes appeared on the "current neighbors" list.  When I connected my laptop computer to either VLAN 10 or VLAN 20, I could get to the internet.  I could resolve and ping servers that were on the internet from either VLAN but I could not ping the node that was on the other VLAN. The OLSR links/topology status page for the v2 node does not show any v3 node addresses.  The OLSR links/topology status page for the v3 node shows the IP address of the v2 wifi interface, but does not show the IP address of the ethernet interface.

Is this a "lost cause" or is there something else I should try?

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

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.

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)

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.

if you flashed version 3.0.0  you could just use the password reset function (after node boots press and hold reset button for 5 seconds and the password resets to our default password)

The connection refused error is because your telling it to upload to host 192.168.1.22  while the node is at 192.168.1.20

>tftp

Transfers files to and from a remote computer running the TFTP service.

TFTP [-i] host [GET | PUT] source [destination]

-i              Specifies binary image transfer mode (also called
octet). In binary image mode the file is moved
literally, byte by byte. Use this mode when
transferring binary files.
host            Specifies the local or remote host.
GET             Transfers the file destination on the remote host to
the file source on the local host.
PUT             Transfers the file source on the local host to
the file destination on the remote host.
source          Specifies the file to transfer.
destination     Specifies where to transfer the file.

Note that you have 192.168.1.22 in the host field,   the 'destination' paramater where you put 192.168.1.20 is a filename not an IP address field.

http://bloodhound.bbhndev.org/products/BBHN/wiki/HowTo/FlashUbiquiti may also be useful to you.

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 have a NSM2 that I successfully reflashed and was using.

For whatever reason (probably me) SETUP would not take my LOGIN.

I downloaded the instructions from this site's downloads, and put the NSM2 into recovery mode (proper lights flashing.   I believe I set my computer to use the IP address of 192.168.1.22 with the submask.

I have WIN 7 and turned on the TFTP client. 

I copied my Ubiquiti factory software to my D drive.  i.e. D:UBNT.BIN 

I brought up the command line and typed:

TFTP -i 192.168.1.22 PUT D:UBNT.BIN 192.168.1.20

It just comes back "connect request failed".

Any help appreciated - thanks in advance

Vance, KC8RGO

Remi Thanks,

I do have the ubitiquiti adaptors to handle the situation. I have both the indoor and outdoor units. It makes things a bit easier when working in the field.

Happy MESHING in 2015

mike

I have two nodes connected back to back over a VLAN. Trying to connect a third node to the stream fails.

configuration:

NS5 and NS2 connected via VLAN. NS2 has RPi running BlackIce.  The RPi is connected to a scanner via a USB sound card.

PiS2 connected only via the MESH. The stream will not play hear.

If I want any node (there are 8 in the test) to connect and output the stream, is there a port forwarding configuration needed?

73 de mike