Thread

Are there not problems running reticulum over the terms of a HAM license due to encryption? The reason low power is allowed (at least in ITU1 which is all I’m familiar with) is because it comes under the IR2030/1/46 explicitly limiting it to 500mW e.i.r.p. whilst not prohibiting encryption, although the frequency and power limits may differ in ITU2. My understanding was if you strayed outside these exempt parameters you were falling back to the terms of your HAM license where encryption is explicitly prohibited, unless there’s a third license at play you hadn’t mentioned in the post.

I honestly don't know what the rules are for this ham in the Netherlands, but if I was to implement his design here in the US, I'd put the nodes on a commercial band frequency to avoid the encryption mess under Part 97 rules. For #EMCOMM I've been toying with the idea of using one of our town's dedicated public safety frequencies for a UHF band LoRA #reticulum #RNode network. #hamradio is too restrictive with the required individual licensing and rules regarding encryption, etc. For example, in a #disaster we can hand out radios from our town's radio cache to non-technical volunteers who otherwise meet volunteer requirements (background check, etc.), and not worry about a ham license.

That’s very much my thought pattern, I’ve wanted to roll out a LoRa reticulum network to my 4x4 Repsonse group in part of as suplimentary coverage to 4g when we have severe weather events. Was going to put it on a commercial band for exactly that reason (we already have licenses for encrypted voice data so should be easy). Interestingly though, I can’t find anything at all about if encryption is allowed on the “business lite” frequencies I have my own license for. Infact it doesn’t state at all what traffic is allowed on it, just the frequencies and channel widths.