Hi, I'm a new mesher and although not in Philly this is the closest forum (geographically speaking) to where I will be working, which is the Lehigh Valley (Allentown/Bethlehem/Easton).   As luck would have it, my QTH is pretty much line-of-sight to most of this area - I'm on a large hill to the north with about 180 degree vantage point to the entire valley.  So I'm pretty stoked about putting up a node and seeing if I can get it running and available.

Anybody interested in extending north please chime in.  

Hello All,

I have some of the Ubiquiti radios, and was wondering what has been the activity beyond the 3.1.0 build.

I wanted to mention Amazon has a special going on - AWS Commit - it's a cloud based Git repository - it is great for small teams.  If you have 5 or less it ends up being free most of the time.  It stays free Tier for the time being if you sign up soon.  I thought the special would end by the end of July but I just put a new project on it - and it is August.  (I do not have any relationship with Amazon other than being a customer.)

Does HSMM have a repository that can be accessed?  I will poke around.

I have a Titanium running 3.1.0 right now - will put this on an Air Grid I have also.

73's,
John
AJ6BC

I oversee several nodes in the Salt Lake Valley. Some are set to use NAT and others use direct. As you know, NAT sets the IP address range to the 172.27.0.x/24 range while direct uses the 10.x.x.x/28 or /29 IP address range. Is there any advantage/reason to use one over the other?

John

kf7nqw

I have a three node mesh - M0HPJ-1 to 3. M0HPJ-1 WAN interface connects to my existing home network. I can connect to mesh nodes etc. from WAN devices by IP address, and anything on the WAN and Internet from Mesh devices ('mesh gateway' is checked, for now).

Reading various articles about accessing DNS resolution for mesh hostnames from outside the mesh says put the mesh gateway IP address in as a DNS server, but it's not working for me.

M0HPJ-1 WAN interface is 10.1.0.230/24

On a linux server on the WAN network, 'dig @10.1.0.230 m0hpj-1' gets no reply, neither does 'host m0hpj-1 10.1.0.230' - both of which should have attempted a DNS resolution from the mesh gateway.

Any suggestions?

TIA, Jim M0HPJ.

This is a simple question for which I can't seem to find a straight forward answer:

What should be the Node configuration that will enable connection to a LAN?  Could anyone provide a diagram and/or written description?

Objective: 

1. Access the MESH network from a LAN so any computer having access to the LAN can also access node traffic. 
2. Eliminate the need for wired connection to a mesh node and thus need to change DNS settings.
3. Provide remote access to MESH network via software such and "logMeIn" and similar applications. These application types should then provide secure access to both LAN and MESH assets.

While I could just experiment, it would be better to draw on previous experiences and knowledge.

Need:

• View emergency power generation assets, configuration, and status.  Applications that serve these purposes are currently working on the MESH network.

Want:

• Remote radio operation and control (future).

Thanks to anyone for their assistance.

There is a help page located on the Mesh router that details exactly what the Mesh AP mode does. http://<node_name>:8080/help.html (link located on the left of the mesh node pages that says help).

Here's what the help file says:

In this mode the device is pre-configured to act as an access point providing standard wireless access to the LAN side of another mesh node. This is to be used on a second router whose LAN port is connected with the LAN port of a mesh node. It is a simple mode but there are special considerations, especially when you want to get out of this mode. See the section at the end called Mesh Access Point considerations for details.

Mesh Access Point considerations

When a device is configured in Mesh Access Point mode it is essentially 'transparent'. You are going through the device to reach a mesh node, and there is no need to get to the device unless you wish to change its configuration. When the time comes to reconfigure a device in this mode be aware that it is not running its own DHCP server because that is the job of the mesh node it is connected to. You will need some other way to configure your computer's network interface. There are two ways to do this:

1. Manual configuration
   Connect only your computer to the LAN port. Set your IP address to 172.27.0.100 and your netmask to 255.255.255.0. No other settings are needed.
   
   
2. Automatic configuration
   You will need another mesh node that is using NAT mode on its LAN, and using the default LAN IP address of 172.27.0.1. Both of these are required, otherwise this method will not work. Connect both your computer and the LAN of the Mesh Access Point to the LAN of the mesh node.

In this mode the default IP address on the LAN port is 172.27.0.2. After one of the above steps you should be able to send your browser to http://172.27.0.2:8080/. If you used automatic configuration you should also be able to go to http://localap:8080/. Like the name "localnode", an automatically generated name exists called "localap" which is set to the localnode address plus one, but only when the node LAN mode is set to NAT. If you changed the default IP address of a Mesh Access Point you will have to modify these instructions accordingly.

We seem to have suffered a rash of WRT54G failures that only happened at certain locations and then vanished when the routers were moved to other locations.

What those locations had in common is that they were running other routers on channel minus 1 (20 MHz BW).  

It seems unbelievable, but I verified that if you bring a WRT54G router into range of a channel minus 1 system, the WRT54G/BBHN router will shut down and not boot up correctly until your take it out of range of the minus 1 signal.

Has anyone else experienced this? Is it the LinkSys WiFi chip or the BBHN/OpenWRT firmware?

Ken - KE2N

I guess I should mention that the the ch -1 / 20 network also uses the "BroadbandHamnet" SSID in case that is relevant.

UPDATE:  this problem is caused by having the same SSID on the channel minus 1 nodes and the BBHN node.  You cannot boot up the Linksys node if the other nodes are in range.  But once you shut down the part 97 nodes the LinkSys returns to normal and you can change its SSID to something unique (or you can change the other system too).

I ended up just resetting the router to the basic nocall state by running a command in failsafe mode called firstboot witch like i said resets the node back to a nocall state I WOULD NOT RECOMMEND if you don't want to just start over. For me starting over is not a big deal due to simplicity of my settings and was up and running again in less than a minute. If there is a way to solve this to let it with the settings let me i would love to hear it.

link to the article about failsafe mode and firstboot https://wiki.openwrt.org/doc/howto/generic.failsafe

So I was messing around and thought that a the mesh AP was something completely different than it was but i switch anyways and now the only way to bet into the router is though safe mode and telnet. I have try hard reset and mutable forms of reset to just get it back to even the no-call firmware. Is there a way to switch the mode or reinstall the firmware from safe mode?

So I was messing around and thought that a the mesh AP was something completely different than it was but i switch anyways and now the only way to bet into the router is though safe mode and telnet. I have try hard reset and mutable forms of reset to just get it back to even the no-call firmware. Is there a way to switch the mode or reinstall the firmware from safe mode?

Hi all,

I was wondering if/how you guys ground your permanently mounted UBNT nodes. I may have the chance to put a bullet on a short tower on top of a building. I don't ground and have not worried about grounding any of my nodes now because they are "Go-nodes" and not permanently mounted.

Thanks,
AVJ

The Saskatoon Amateur Radio Club (SARC), http://ve5aa.dyndns.org/, and the Meewasin Amateur Radio Society, http://www.meewasin-ars.ca/, joined forces to run a 5A station in SK (Saskatchewan).  

One of the key technologies that we used was HSMM on four LinkSys WRTGL routers.  Thursday night prior to field day we had a 'shake and bake' evening to ensure that had the bugs worked out of the logging/computer control/network.  Most of the evening was spent getting the computer control working from the N1MM Plus to the rigs.  Getting the network connections up and running on Saturday morning was uneventful.  The HSMM-MESH was rock stable.  It ran the entire weekend with no problems -- a testimony to the quality of the software.

Check out my Tweet with the screen shot of the HSMM-MESH up and running:  https://twitter.com/ldobranski/status/746749791799914496

You can check out the other field day Tweet's by searching for @ve5aa.

Next on the Saskatoon HSMM-MESH anchor nodes on some high buildings.

73 de VA5LD

Lawrence

@ldobranski

I was wondering how difficult it would be to get HSMM running on one of these routers.

Here are some of the features of the router.

• 802.11 b/g/n 150Mbps (130Mbps real)
• wireless power output 20dBm - 100mW
• 4 MB flash memory (can be modified for 16MB)
• 32 MB RAM (can be modified for 64MB)
• USB 2.0 port (High-Speed only, use an external High-Speed hub for Full/Low-Speed devices)
• Powered via micro-USB socket
• Tiny form factor: 5.7cm x 5.7cm x 1.8cm

If this is do-able what would be the best route to take to get everything installed?

Hello All,

Saginaw Valley Amateur Radio Association will have their Field Day at Elmer Lange Park in Kochville township again this year.

We will have several nodes setup for logging as it works very well last year. We welcome you to stop by and check it out. Feel free to bring your own node if you have one, or your own laptop to connect to the mesh if you would like. We will have a GOTA station and anyone wanting to make contact or just give radio a try is welcome to join us.

Happy Field Day!

KE8AVJ