Pages

Broadband Hamnet from HSMM-Mesh node is up and running

Broadband Hamnet from HSMM-Mesh
Now what? - Some ideas on what to do AFTER your node is up and running.
 
[After answering many of the same questions of newbies in email, I put this together to give a few folks an idea of what's in store...]

If you are like me, you found out about this mesh stuff and thought this might be an interesting tool... You saw possibilities. You thought, yeah, this is what TCP/IP packet SHOULD have been!

If you are like me, you hunted down some gear, you figured out which software to download, you leaned how to get inside the box and re-flash the firmware – and voila! You are almost there! You click update and cross your fingers...


Hopefully, it worked...

OK, so now you flashed a WRT54Gx or a Ubiquiti module and now you have a node... With your call sign in it and everything. Congratulations!

Now what?!?

It's on the air and you can go and scan local WiFi frequencies and look at a node list that has only you – or if you are lucky, you might see other meshers in your area.

When you look at the Mesh Status page you will see your node. You may see other nodes if there are people around you as “Neighbors”. Typically in the remote node list you will see node names on the left and their advertised services on the right. These services can be anything from a web page, HamChat, Bulletin boards, cams and even IP phones.


Part of the fun of the mesh is there is stuff out there – or there should be. If there is nothing out there but just nodes to interact with – why mess with it? One of the things I have tried to bring to the table on my local mesh (and what I am tunneled into) is something for people to listen to, something to read and something to interact with – so people can interact. Otherwise you are just looking around at other nodes, looking at their mesh status screen and perhaps scanning their local WiFi frequencies to see what routers are near them... And that can get pretty boring after a while...

Most of us hams want to talk to other people, interact with other people and perhaps learn something in the process... The mesh is only the tracks, we have to put rail cars on them and move them somewhere for it to be something of value to the rest of us... The mesh is the infrastructure for whatever we want to put onto it – just like the internet!

HamNet is a great emergency communications tool. But if the only time we ever use it is to drag out in the time of an emergency, dust off the routers and plug them in – then what? If there is no larger infrastructure of something to connect to, those emergency communications tools are useless. If the only time we dust off this stuff and use it is when the stuff hits the fan in a hurricane or something, people aren't going to be proficient in using it!

So... Lets take a look at what some ideas of what you can probably do to make this a system that people want to use, log in to and toy with on a daily basis – like the rest of our Ham radio Hobby. Something that is THERE for us to use when we want it... Let's see a few ways of using it that will gain you experience as to how to set this stuff up and maintain it.

I will use my network as an example as to what you can do – but it isn't the ONLY way to do it! The following is based on MY experiences, yours will undoubtedly be different.

Now what? Let's talk resources...

Now you have a node. You didn't think you needed just one did you? Now you have more nodes to add! In my shack I have the “QTH” node that is the internet gateway for my little mesh network. It plays traffic cop between the 10.x.x.x HamNet network and my home 192.168.x.x network which is the one that talks to the internet. It is like ground zero. Everything branches out from there.

To this I had to add a tunnel server and a tunnel client router so I could mesh with anybody out there on the web via tunneling. These have to be WRT54GS v1-4 routers as they handle the tunneling scripts and the right version of the software. These have their WAN ports plugged into the 192.168.x.x network on static addresses to talk to the internet. I live in the boondocks and without these, I wouldn't see anybody else, period.

To this I added a “Bridge” router that has static Ips and setup as NAT that has its WAN port plugged into the 192.168.x.x network. I reserved addresses for services on this to my servers I have on my 192.168. network like my streaming audio server, web server and mail server, etc...

Now that's FOUR little WRT54Gx routers sitting on top of one another – with no DTD linking at all, there's a lot of RF flying around there because all the inter-router communication is over RF right here in the shack. So I cut the power on all of them down to the minimum – everybody seems happy. But all the routers talk to the 192.168.x.x network via WAN ports and the shack PC's and mesh based servers, cameras, etc. are on the LAN ports. But inter-router communication is still all over RF in this configuration.

(This isn't including the Internet router that talks to the 192.168.x.x network!)

Linksys routers have a chipset bug that prevents us from using direct DTD linking via the lan ports. However, Ubiquiti gear is free from this problem and will happily pass LOTS of its traffic via the LAN ports keeping the RF side more open for higher speed data transfers.

That's FOUR routers to get me on the internet, tunnel over the internet and connect the shack and my home network together... All WRT54Gx's (I have G's, GL's and GS's – but only GS's will tunnel.)

These four routers give me the infrastructure to put resources OUT THERE on the mesh – without it, I couldn't provide other folks stuff to look at, listen to and interact with...

Now what?

Well, we need to talk to the outside world with RF right?!?

The WRT54G routers don't have all that much power. The Ubiquiti units are more suitable for mounting outside, way up high and out in the open. Most of them either have integrated antennas or are designed to be screwed right onto the back or bottom of the antenna so you have no feed line loss at all.

Now what? Should you put up an omni, a beam or a dish?

First off, microwaves do not act like we are used to on VHF/UHF. They do... But they don't... If there is nobody else in your area meshing, put up an omni. Just because you never know what you will do in the coming months. If there is someone, somewhere near you, figure out the compass heading and put up a patch antenna, a yagi or one of those 150 buck BBQ grill dishes for a whopping 24db of gain and point it at your buddy. Having it on a rotor might be nice, but once you find a path, you will probably want to leave it pointed there...

Why not split off one of the antenna ports of a WRT54Gx? Because microwave feed line losses are horrendous and after personally using Ubiquiti M2HP bullets and Rocket boards – there is no comparison in performance, ruggedness and reliability for something out there in the weather. It is commercial carrier grade stuff!

NOW – with four routers in the shack, and one up on the tower I can see peoples internet routers for miles around – and the mesh on the tunnel over the internet... I live in the boondocks, no other meshers are within line of sight, even from on TOP of the tower!

Now what?

I setup my tunnel routers to talk to the outside world via the Internet. Without it, I can't see anybody else... There's a lot of stuff out there from Hawaii to Paris to Italy even! It's growing every day...

Now what?

I added HamChat to several of my routers so people could type to each other keyboard to keyboard from anywhere in the world... I felt the need to give people a way to interact with each other. This was a very simple way to do so and it lives and runs ON the node! No other hardware required!

Now what?

I renamed all my resources to have unique names that probably wont be duplicated somewhere else in the WORLD. Like putting my call sign in front of them so my cameras names will be different than someone elses barn-cam. Having VERY unique names will become more important as the mesh grows and there may be 13 “barn-cam” entries in the list! How many PBX entries can there be before people start naming them something unique? Although I am tempted to put up a chicken coop cam named LIVENUDECHICKS!

Now what?

Well I needed to see what the temp was in the greenhouse and be able to see if the propane heater was still lit or if the 40 lb. Bottle of gas had given up its last ounce of propane... I put a little WRT54G router out there on a shelf with a Foscam waterproof POE IP camera attached to it, DHCP reserved and setup as an advertised service. Voila! I can now see the big round thermometer in the greenhouse and the face of the propane heater and it even sees in the dark!

Now what?

Still contemplating the chicken coop cam...

Now what?

Well I needed to watch over my parking lot next to the barn to see when the UPS man showed up... I mounted a Foscam waterproof POE IP camera on the tower and connected it to one of the WRT54Gx's in the shack and set it up as an advertised service.

Now what?

Well, I needed to monitor the barn... I put a little WRT54G router out there on a shelf with a Foscam waterproof POE IP camera attached to it, DHCP reserved and setup as an advertised service. Voila! I can now see the inside of the barn to see when the cats get left behind or the traps are sprung for the rats. Did I close the barn door? I can peek at the cam and see from the comfort of my skivvies in the house on a tablet or in the shack.

Now what?

Still contemplating LIVENUDECHICKS cam... Maybe bird feeder cam... Maybe hummingbird feeder cam... Maybe even the aquaponics koi pond feeder cam... I wonder if the IR LEDS will work under water...?

Now what?

I built servers and added cameras to the mesh advertised services... I added streaming audio servers off of a big bank of scanners in a rack in my shack. I added cameras. I put a few html files in the www directories on the nodes and put them up as Node List information pages the tell people what are ON my nodes and what to do with them.

And now people have something to look at, read, listen to and interact with...

It sure beats looking at peoples node status screens and scanning their surrounding WiFi frequencies... :)

Now what?

I scurry off to Amazon to order another IP camera for the chicken coop... You will accumulate a collection of routers, bullets, LAN stuff and cameras if you dive off into this deep enough and YES it can become addicting! But Amazon and the UPS guy will love you...

I am still trying to figure out how to stuff a waterproof IP cam in a glass bottomed bucket for the Koi pond and NOT have the IR LEDs reflect back from the glass......

My buddy suggested a deer feeder cam...

Now what?

Each day somebody does something else with the mesh I am tunneled into. Countries are added, new resources are added. More and more people are coming together on the mesh now that tunneling has become a reality. Giving YOU more opportunities to explore stuff out there...

Just like the early days of the world wide web... The tracks were laid down, people figured out what to do with hypertext and the internet became something most of us can't live without. What happens to the mesh is up to good people like you to put something up there interesting and worthy of somebody else like me wasting a little time on and exploring what there is out there.

Who knows, in another ten or twenty years, the mesh may become the Ham Radio version of the internet. If we don't toy with it, we wont be able to use it when the times comes to depend on it for whatever reason...

Then what?!? :)

It's all up to folks like you and me... If you don't build it, who will?

We all need something else to look at other than my chicken coop... Even LIVENUDECHICKS have a limited appeal after a while... But they make good eating... The Koi, not so much...

Have some questions, tips, tricks or hints to share? Please comment!

No comments:

Post a Comment

Thanks for your comments, Comments may take a day to show up

MESH Discussion Forum Group:

AREDN - Amateur Radio Emergency Data Network AREDN@groups.io
https://groups.io/g/AREDN
.

Note: only a member of this blog may post a comment.