Replace (only available on ubnt) /usr/local/bin/wscan with:

https://drive.google.com/file/d/0B2bEy75HhwWhRTl3aHpLanEybFk/view?usp=sharing

Joe AE6XE

Ok, sounds like the gateway node isn't advertising the route.

The obvious question at this point is to be sure Mesh Gateway is checked on the gateway node and it's been saved and restarted.

After that it usually is because the Internet is unreachable, but could be because some filtering is in place Between your gateway  node and the Internet. Log in (telnet or ssh if directly connected) to the gateway node and try pinging the following addresses:

71.42.236.91

71.42.236.90

8.8.8.8

8.8.4.4

if none of them respond than either the node doesn't have Internet access or some filtering is blocking pings, in either case that would cause the route not to actually be advertised over the mesh. 

If you do get a ping response than check /etc/config/olsr on the gateway node and be sure it has the olsr_dyn_gw plugin listed (it should if mesh GW is checked on the gateway node)

Thanks for straightening me out on that fact.  I'm new enough to the Ubiquiti devices that I'm still getting the features of the different models confused.  I guess I was thinking about the Rocket when I was thinking about external antennas. But 13 miles with the built in antennas?  Wow, looks like I better get me a couple of NSM2s!

Steve - N4TTY 

I have just bought a NEW WRT54GL complete with instructions CD etc. Can anybody tell me which Broadband-Hamnet software to download as I am a bit confused  about which software to download.

Derek G6LVS

1) What Version of the mesh firmware? Current Production V3

2) On the remote node have you configured a static IP for the WAN interface as this could interrupt the routing when the interface is not plugged in. Negative

3) On your remote node what does it show for Default Gateway on the mesh status screen? None

4) On your remote node olsr status screen do you see a route for 0.0.0.0?Search all screens found no route to 0.0.0.0 ---- route not found on other nodes either, but the NS5 and NS4 connected through the switch has the home network gateway IP listed.

(if you don't see the above we can stop here)

4) Running a traceroute from a PC plugged in to the remote node what is the path ? Does it die out a specific node or location?

Hope this helps

73 de Mike/K3MMB

Well since we ruled out the VPN code it comes down to running the steps:

1) What Version of the mesh firemware?

2) On the remote node have you configured a static IP for the WAN interface as this could interrupt the routing when the interface is not plugged in.

3) On your remote node what does it show for Default Gateway on the mesh status screen?

4) On your remote node olsr status screen do you see a route for 0.0.0.0?

(if you don't see the above we can stop here)

4) Running a traceroute from a PC plugged in to the remote node what is the path ? Does it die out a specific node or location?

Those questions should give is a good starting point to look at what is going on and figure it out from there. 

Thanks Conrad,

I reset the NS5 stripping VPN code. No difference. The two stations connected via the 108T switch still have access to the internet. The NS5 connected over the MESH can only access the other nodes. I tried two different netbooks (1 windows and one Linux) but no workie with internet.

73 de Mike K3MMB

It represents the strongest single being received in the wifi scan.

There was an interesting patch shown by Joe AE6XE in one of the forums recently that showed each node individually. I haven't had time to test it personally, but in theory it looked right and it should be able to show each individual node strength broken out. It looks promising but isn't a part of the builds yet.

Please reset the gateway node without any additions (VPN code) and try agaim please. This can be done by flashing the node OR by holding the reset button for 15 seconds.

I know the VPN code has progressed a lot and is looking good, but it is still a work in progress. It therefore would be helpful to see if the issue exists without changes from the official build, If the issue exists still when gateway does not have the VPN code we can look at it further, otherwise if it does work after a fresh flash it is likely a VPN code issue and Darryl would be best equipped to work with you to solve the issue.

Hi all,

I wasn't satisfied with the output of olsr-topology-view, so I whipped up my own version in Python.  Sample output can be seen here:

    http://ve2zaz.net/BBHN-Ottawa_www/

Source code and a bit of documentation for the generator can be found on Github:

    https://github.com/argilo/bbhn-utils

Suggestions, bug reports and code contributions are welcome!

73, Clayton

Ok, I think I've got it.  One question though... A Wi-Fi scan on any node shows a single entry for the network, regardless of how many actual connections are currently present. Following your response, above, that makes sense.  So, I am just wondering, in this case, does the signal strength (Sig) represent the best signal of all connected nodes?

Happy New Year.

This may be normal, but>>>>

I have one NS5 setup as the gateway on my MESH, that node is connected to a NS2 via vlans defined on 108t switch. The switch is connected to my home lan. Both of these nodes can access the internet. The NS5 also has the VPN coded added from K5DLQ, not used yet.

I added a Rocket5, it see the MESH and displays the status. I can navigate to the other nodes. It does not have internet access, even though the NS5 is a gateway.

Is this the new norm, or do I need to fix something??? If it is normal, is there a way around it?

Happy 2015

73 de Mike/K3MMB

We finally got around to upgrading our solar hilltop node wrt54g to 3.0 and now 3 of us are connected. One is 4.5 miles from the node with a wrt54g, the others is 10.25 miles away with a Ubiquiti Bullet M2 HP and parabolic, and I am 7.5 miles away also with Ubiquiti Bullet M2 HP with Parabolic. I am getting 89% link quality without fine tuning the aim. We tested file transfer speeds between myself and the other ubiquiti node through the hilltop node with maximum file transfer rate of 11KB/s. 

Ron ( and Shawn)

Very encouraging that you could link between Hamilton site and Burlington rptr site using mobile hsmm.  I too use a mobile for such testing purposes.

I will add the location of your nodes at Fennel Ave. and Upper Gage and the repeater site in Burlington to my ( personal) Google Earth HSMM plot.  If you want a Google Earth kmz file email me at bob@rcflier.com 

Attachments
 mesh status 2014-12-30.jpg [179 KB] ::

Hi Shawn

Dixie and Burnhamthorpe is quite a bit off of our path between ve3mis-rptr and ve3mis-stn.  ve3mis-rptr is 2 blocks south of Burnhamthorpe and 1 block east of Hurontario. You will need to aim 209 degrees from your Dixie/Burnhamthorpe site to hit ve3mis-rptr. It is 4.1km.  What do you have for equipment / antenna / height at that location? We would consider another node pointing in that direction for you!  If you are in the area and feel like a Timmies let me know I live nearby.  Best to keep in touch by email bob@rcflier.com  

Yes it does.

What happens  is when the device first starts it looks for another existing device advertising a network with the same name.  If the name doesn't exist it will generate an ID locally (exact method depends on the software brining up the interface but it's suppsoe to be in a manner that no two devices will generate the same ID) and begin advertising the network.

Every wifi beacon frame contains what is known as the TSF field, it is the wifi network time. It starts at 0 microseconds and goes up for each microsecond of time that passes on the wifi network.

When you have two devices who couldn't see each other before that now can see each other the TSF is compared, the network with the higher TSF is assumed to be the longer lived network and the device will roll it's ID to match the identifier of the longer lived network thereby inheriting thr same ID.

From these two methods EVERY device in the mesh will have the same IBSS/BSS identifier (sorry mislabeled it earlier) as it propagates through the network.

If you logged into the remote bode you should see it claims the same address as well as the network it is joined to/advertising

Literally every device in an ADHOC network will have this same association this is how the device knows when looking at wifi packets that the packet is meant for its network as names (BroadBandHamnet-20-v3) are a human nicety and are not actually used at the lower levels of hardware.