Hi,

I'm pretty new to this mesh stuff and finally got to a sticking point hence some questions to the experts...

Here we go:

#1

I'm testing with 2 nodes(Ubuquiti M2 HP) which are talking to each other fine.

One is stand alone into an xp laptop for testing the links.

The other is connected with NAT to my home LAN on 192.168.1.x.

The stand alone unit can resolve the hostname of the other node but not vice versa, the DNS gets lost across the NAT somehow... so how do i fix this?

On the LAN with a win7 pc i have setup the route and DNS as the LAN IP of the node but it does not resolve any host names. I can get to both nodes with the IP addresses but not as nice!!

#2

I've installed HSMM-PI on an MK808 mini pc with picuntu OS, the system boots up fine and i have configured it for the correct SSID BroadbandHamnet-v1, give it IP and Name etc.

On the MK808 pc i can 'see' the other two nodes and access them but  the mk808 node is not seen by the ubuquiti nodes.

I looked in OLSR and is it reporting that the mk808 node is not 'SYM' to the others.

I looked in the source code to see what SYM means:

* If the sender interface (NB: not originator) of this message
* is not in the symmetric 1-hop neighborhood of this node, the
* message MUST be discarded.

Is there something i have missed or is the current Ubuquiti HSMM setup not compatable with HSMM-PI?

Would not having a LAN interface on the HSMM-PI node stop the it from working? (currently is is set to a false interface name as it only has WiFi network port)

Apologies for any obvious mistakes!

Any ideas on either problem is appreciated.

Thanks

Rob

M0DTS

Item 1)

If you are setup how I think you are the Mesh node likely has an IP address, DHCP is being provided by your main router and is telling all your local systems that it is the DNS server and Default Router

The client PC on your LAN network would need to have static routes put in to go to the mesh node for the 10.x network AND would need to have the LAN Mesh node set as its DNS server manually. Otherwise the computer on your LAN doesn't know that the Ubiquiti node is is providing you access to the mesh network.

Item 2)

HSMM-PI project to my knowledge is NOT connected to the BBHN project. I would suggest contacting the makers of that software for their input on the configurations as it is really out of scope for this group.

The Ubiquiti build of BBHN is compatible protocol wise with the Linksys 1.0.0 build. I can't  guarantee the same about the HSMM-PI project.

Thanks for the info.

Regarding the DNS, i have already done as you thought, routes have been added to the 10.xxx network with the route command on the win7 pc and the alternate DNS has already been set to the local node IP address on the LAN so i'm not sure where to go next with that one.

Ok on HSMM-PI, probably incompatability then, i will try find out some info and report back on that.

Rob

1)You are likely getting a response from the first dns server saying "NXDOMAIN" (no such domain)  Windows does NOT ask the 2nd dns server for an address after this (At least on my test XP box)

Try switching the order of the DNS servers.

2nd) You also have to deal with what is known as the "search root" (local.mesh)  this may need to be added to  the Advanced>DNS list (depending how your computer is setup) try using <node>.local.mesh in your connections instead of just <node> to see if t his solves your issue.  example: http://localnode.local.mesh:8080

Yes it seems windows will fail on the first dns and not even try the second one!

I tried swapping the DNS order but that did not help, I cannot find anywhere in the network settings to put the 'local.mesh'.

This morning I booted into Ubuntu 13, added the node DNS, added the route and i can also add the 'local.mesh' into the 'search domains' setting which i can't find on windows, i was able to connect via the host names within a few minutes.

I might just use linux, much easier!

73

Rob

Hello Rob,

Well I am partial to linux myself so you will not see me argue with that suggestion.

the search root is also known as dns suffix.

Navigate to your network connection > properties > tcp/ip v4 > properties > advanced > dns > edit the suffix list or set the default suffix to local.mesh. (DHCP usually does this for you hence why you need to do this manually )

Aha DNS suffix setting, That did the trick.

Many Thanks

Rob