OK, so the DNS stuff is getting very irritating.

If I set ALL the mesh nodes to use the AMPRnet DNS (in setup, under WAN), I would think that they should pass this info.

BUT apparently not, because when I have the PC set to get DNS from DHCP, the nodes supply their internal DNS server address (which is fine, otherwise I would only be able to interact with the mesh by knowing IP addresses)

However, for some mysterious reason, it is passing INTERNET DNS information, but NOT AMPRnet DNS, so I cannot access AMPRnet hosts unless I specifically use their IP address. (so routing is working)

Now, if I set DNS in Windows to the AMPRnet DNS server, I get AMPRnet AND Internet DNS info, but obviously lose the Mesh DNS stuff, so I can't access nodes by name.

Where in the heck is BBHN getting external DNS info from?  Did someone hardcode google's DNS server info into the firmware or what?

Nope.  That didn't work.  :(

I hate to have to put in the route command every time the power cycles. 

I guess I could add it into a script that's run at the end of booting.

Thanks Jim.

So to get dual routing working, the Mesh node the PC is connected to also has a default route out to the Internet.   So adding a route such as:

route add -net 44.0.0.0 netmask 255.0.0.0 gateway W5LMM-HSMM-1 dev wl0

Will allow the node to know where to route the packets destined for the 44 net.

W5LMM-HSMM-1 is the node that is connected to the AMPRnet on the WAN port.

So I am able to access BOTH the Internet, and AMPRnet from a PC connected to the 2nd mesh node.

Now I have to figure out how to tell the first mesh node (the one with AMPRnet) to route Internet traffic out through the 2nd mesh node!  Without screwing up the mesh routing.   UGH.

Then, the other issue is, how is DNS handled?   If I set my DNS server on the PC to be automatic (gets it from DHCP as supplied by the mesh) then I can connect to anything in the mesh just fine.  However, it forgets the Internet/AMPRnet routing!

I had assumed that setting the DNS to the AMPRnet nameservers (which also include Internet at large) that the mesh would use it's internal DNS for mesh purposes, and tack on the external DNS info as needed.  This does not seem to work.  If it does, it's sporadic.

Is that not how DNS is supposed to work across the mesh?

Any ideas on routing the other way, so a PC connected to the AMPR connected node knows to go out (Internet) thru the 2nd node that is Internet GW??

Thanks Jim.

So to get dual routing working, the Mesh node the PC is connected to also has a default route out to the Internet.   So adding a route such as:

route add -net 44.0.0.0 netmask 255.0.0.0 gateway W5LMM-HSMM-1 dev wl0

Will allow the node to know where to route the packets destined for the 44 net.

W5LMM-HSMM-1 is the node that is connected to the AMPRnet on the WAN port.

So I am able to access BOTH the Internet, and AMPRnet from a PC connected to the 2nd mesh node.

Now I have to figure out how to tell the first mesh node (the one with AMPRnet) to route Internet traffic out through the 2nd mesh node!  Without screwing up the mesh routing.   UGH.

Then, the other issue is, how is DNS handled?   If I set my DNS server on the PC to be automatic (gets it from DHCP as supplied by the mesh) then I can connect to anything in the mesh just fine.  However, it forgets the Internet/AMPRnet routing!

I had assumed that setting the DNS to the AMPRnet nameservers (which also include Internet at large) that the mesh would use it's internal DNS for mesh purposes, and tack on the external DNS info as needed.  This does not seem to work.  If it does, it's sporadic.

Is that not how DNS is supposed to work across the mesh?

Any ideas on routing the other way, so a PC connected to the AMPR connected node knows to go out (Internet) thru the 2nd node that is Internet GW??

Sorry about the video being gone, but it was old and needs to be updated. The way that the network handles connections is better now and much easier to use. Also, N!MM has changed to the .NET Framework so I have some experimenting to do. 

I have some basic information about HSMM-PI on my page:

http:www.qsl.net/w6dps

Click on the "Ham Projects" page.

I like playing with Raspberry Pi for nodes, and a variety of other ham related uses.  I will be posting another couple of articles in the near future about using a PI for APRS tracking...

Dave

Già... proprio così.

Grazie a Clint AE5CA il mio nodo IZ5FSA-HOME [Ubiquiti NS2Loco] è in rete con gli amici USA grazie alla nuova funzionalità attiva dalla versione 3.0.1rc2 che sarà la prossima versione 3.0.1 rilasciata a breve.

In buona sostanza se un nodo BBHN ha l'accesso ad internet questa nuova funzionalità ne permette l'integrazione ad altre via tunnel IP.

Non se ne deve nè se ne può abusare, ma invito gli amici italiani che si vogliono cimentare nella realtà BBHN a prendere in consideraizone la cosa... chissà che non si possa iniziare una nuova rete radioamatoriale anche nello "stivale"!!!

C0è nessuno interessato????

73 de Leo IZ5FSA

to make any changes persistent across reboots, it usually goes into /etc/config.mesh/blah

So for this I think it would be:

/etc/config.mesh/network

Add a blob:

config route
option interface lan
option target 44.0.0.0
option gateway {IPofWANinterface}

Give that a shot and see what happens.

73

I have a couple of Pis running as mesh nodes.

I already had them and some USB wifi cards (Alfa 2W) kicking around so it made sense to give it a go. Probably more useful as a temporary or test node.

There is all the info you need to do it here:  https://hsmmpi.wordpress.com/

I like using them as I can just swap out the SD card for another purpose and then pop the Mesh SD card in if I want to use one as a node.

Jon

You can pick up the new dhcp lease by unplugging the Ethernet cable to your computer and after a few seconds reconnecting it, or you can Run a "CMD" window and type the command:  ipconfig /renew

As Conrad points out, we have lots of issues with browsers caching IP addresses, so closing and reopening the browser is definitely worth a try.

Andre, K6AH

The Lan up address should change to a 10.x address you will need a new dhcp lease on your PC to pick that up.  I've also seen some browsers cache localnode so you sometimes have to close the browser.

The WAN ip in DHCP mode is subject to your local DHCP server settings and is out of the control of the node in DHCP a mode.

   I have a Ubiquiti AG-HP-2G20 and my problem is that when I do an initial password change from

the default it will reboot. But some how it does not come up with a default route to get back

in. I do not touch any of the WAN dhcp configuration.  I have noticed that the dhcp ip address

has changed from 192.168.1.1 to 192.168.1.63 or 73 depends on the moon cycle.

When I do a trace route back to the AG-HP there is NO route.

 Why would a password change effect the ip and routing after a "save" and a "reboot"? Am I missing

something?

Just as a reminder, the Username: root, and the Password: hsmm

Andre

After upgrading from BBHN 1.0.0 to BBHN 3.0.0 using bbhn-3.0.0-brcm-2.4-squashfs.trx I cannot login to the router to redo the configuration using root/admin.

hppt://localnode:8080/cgi-bin/status shows NOCALL as the node and 3.0.0 as the firmware version.

Any Suggestions?