I am not a lawyer, but I have spent a lot of time carefully reading documentation and thinking over this topic. So with that, here is my carefully formulated answer:

The only time any device or person follows Part 97 rules is when they transmit or affix to and while under direct control (ie. RC aircraft) their FCC-Part 97-assigned call sign. Should you choose not to use your FCC Call Sign, then technically speaking, you are still operating under Part 15 rules.

In short, there is nothing that makes Broadband-Hamnet unique for amateur radio use only other than the fact that most users here will put their Amateur Radio Call Sign as their node name (the node name gets transmitted once every 5 minutes), and thus are expected to abide by Part 97 rules and regulations. Why is this? Anytime you identify using your FCC-assigned call sign, you are implying to the rest of the world that you and your equipment are following the rules and regulations as outlined in accordance to your license grant.

So what does this mean with respect to Broadband-Hamnet?
You and your equipment must abide by Part 97 rules and regulations as soon as you change the node name to contain your call sign. If you ever change your node name to anything else other than a call sign, then you are no longer operating under Part 97 rules and regulations, but instead fall back to the rules and regulations as specified by the type of certification of that particular equipment.

I hope this adequately and sufficiently answers your question.

This reply has been tailored to those who operate under Title 47 CFR 97. Please double-check the documentation from your governing radio agency/commission for the most up-to-date information concerning what is and is not permitted (amateur radio related or not).

Hi all,

I've been wondering about HSMM-Mesh and the point that it needs to be used only by amateurs.

The system's communication is not encrypted, and it is on the lower 6 channels of the WiFi band, running no more power typically than can be put out using a WRT54G in stock mode. It connects to the internet, runs IRC and more, all of which are pretty public.

I don't understand what makes this configuration unique for amateur radio use and exclusivity. DD-WRT also provides a mesh capability, but it has no such requirement. It even shares the frequency for AP use.

I'm starting to wonder if this net could be setup in non-urban 3rd world areas and not be subject to amateur radio regulations?

So, can anyone clarify why this is so "amateur radio" specific? 

Thanks, Don  VA7IQ / AE7UP

What are your recommendations for an inexpensive and simple to use support for a portable mesh node, antenna, camera?  

Thanks!

Bob W8ERD

Ok so one of my new nodes is up and running in north Murray. K7EA-31 / Murray-North. It's a Ubiquiti Bullet M on a 18 dbi collinear omni, up above roof lines. So far the only neighbors are my NanoStation Locos. 73 and here's hoping we see some more action. Bill K7EA

They work fine.

A comparison:

WRT54G's - 32mw to 63mw (depending on which model and who you ask)
NanoStation Loco M2 (200mw, built-in 8dBi MIMO antennas)
NanoStation M2 (600mw, built-in 11dBi MIMO antennas)

I know someone who is using the NS Loco, and I am using one right now too. Works fine for us!

Hello Everyone,

So I was on Amazon looking at Ubiquity radios and I saw that there are both Ubiquity NanoStation's and Ubiquity NanoStation Loco's for 2.4 and 5.8 GHz. The NanoStation looks like it is taller than the NanoStation Loco and it is also about $30 more expensive.

My question is: What is the difference between the Ubiquity NanoStation and the Ubiquity NanoStation Loco with regards to use in BBHN?

73!, KD8NXH

Well I wanted to wait and add our photos (I took a lot with other member's cameras) but I don't know what happened to the pictures but now that the official results are out I thought I should at least add them here.

Plans for next year have already begun. 

Dear all

I refer the notice told the latest firmware XM 5.6.X of UBNT device not work for BBHN firmware. And I refer the link provided.

Does it if I downgrade the firmware to XM 5.5.10, and then fresh the BBHN firmware to the UBNT device will OK ?

Thanks in advance.

Br

Francis, VR2XKP

Dear all

I refer the notice told the latest firmware XM 5.6.X of UBNT device not work for BBHN firmware. And I refer the link provided.

Does it if I downgrade the firmware to XM 5.5.10, and then fresh the BBHN firmware to the UBNT device will OK ?

Thanks in advance.

Br

Francis, VR2XKP

Dear all

I refer the notice told the latest firmware XM 5.6.X of UBNT device not work for BBHN firmware. And I refer the link provided.

Does it if I downgrade the firmware to XM 5.5.10, and then fresh the BBHN firmware to the UBNT device will OK ?

Thanks in advance.

Br

Francis, VR2XKP

Dear all

I refer the notice told the latest firmware XM 5.6.X of UBNT device not work for BBHN firmware. And I refer the link provided.

Does it if I downgrade the firmware to XM 5.5.10, and then fresh the BBHN firmware to the UBNT device will OK ?

Thanks in advance.

Br

Francis, VR2XKP

Hi all,

I have been working my way through setting up BBHN and whatever apps I can find that might be useful, one of which is N1MM+. There are lots of things being said about this setup, but with the latest version (possible the last-est version) of software for the WRT54G series, the instructions with DMZ comments and address spaces get very confusing.

What I discovered was an outstanding PDF article at https://www.dropbox.com/s/laevr8hhb4zudrj/Field Day%2C N1MM%2B%2C and mesh.pdf?oref=e which gave nearly step-by-step instructions to do the setup. Very helpful. The important thing is to remember that even though K5CS uses a 172.x.x.x fixed address for the master, it is NOT a NAT or DMZ network. It is native, using whatever address spaces the routers setup (I used default everything).

What I did was just attached my first PC, and named it master in N1MM+. Then I did a DHCP address reservation, and after that it was all setup in N1MM+ itself (i.e. the entering the IP address of each correspondent on the WAN -- the broader 10.x.x.x address space for routers and computers).

If you can get 2 computers working with N1MM+ on a common router (the one the master is on), then the step to separate routers is just moving the slave, then adding it to the network computer table in N1MM+. Be warned, however, I had to shut off all antivirus protection as that was a major reason for failed connectivity.

I've been able to set N1MM+ up, sync, post contacts from both, and even "stop the network" (considered evil), and restart it. The resync worked like a cat's meow. And with all N1MM+ setups, you must get its config matching across computers or lots of red messages will appear.  ;-)

Now that article is very hard to find just with searching, and it doesn't appear to be on this site. Perhaps the author would like to make it available and visible here, but I thought K7CS has done a sterling job of explaining how to set this up. KUDO's to you, Charles K5CS!!

No longer a need to wonder how-to -- there are now tools available to get to it.

All the best!!  

Don VA7IQ, AE7UP 
Delta, BC, Canada 

Anyone know how to open port 22 on a bad install so I can SSH or TFTP firmware in? I can telnet into it to also try and write a firmware into the TMP directory. Want to write origiinal DD-WRT firmware in it ansee 9f I can revive it

I purchased a WRT54G V2 Hardware with  version 4.21.5 firmware loaded in it any ideas what file I should use would be appreciated. Thanks, Jeff W8IP.

I purchased a WRT54G V2 Hardware with  version 4.21.5 firmware loaded in it any ideas what file I should use would be greatly appreciated. Thanks, Jeff W8IP.