Open IP over VHF/UHF Part 5
rowetel.com
rowetel.com
Of course, it's a lot more expensive to implement than the article system (and I used some Cadillac components in the test bed). Someday (when the parts shortage is over), I may productize it.
https://www.w6rz.net/ofdm3.png
https://github.com/torvalds/linux/blob/master/drivers/media/...
With a license, you could transmit with up to 1500 watts (although it would not be easy). But you could easily run considerably more power than WiFi (like 10 to 20 watts).
Yes, I definitely simplified the explanation of the functionality of the driver. It's really a ULE (Unidirectional Lightweight Encapsulation) protocol driver. It processes Transport Stream packets received from the DVB-T2 receiver on a selected PID and forwards the data payload (IP packets) over the Linux Ethernet interface.
On the transmit side, I implemented the ULE protocol in GNU Radio (Github link in the diagram). To make the interface bidirectional, I capture transmit packets sent to the interface with libpcap as part of the encapsulation process.
https://en.wikipedia.org/wiki/Unidirectional_Lightweight_Enc...
Who would respond? I'm genuinely curious - I recall a long time ago hearing a story about FCC vans with antennas driving around a neighbourhood trying to triangulate the signal and find the source but that was a much stronger "pirate" radio station.
For the frequencies I'm using, the 3.4 GHz band is very lightly used by hams, so that won't be a problem. Plus wide band OFDM signals just sound like noise in a narrow band receiver. There are government/military radars, but only in certain geographic areas.
2305 MHz is a little different. The 2305 to 2310 segment is shared with band 30 LTE. Band 30 is pretty lightly used by AT&T (the only licensee), but they do use it in some cities. The 2300 to 2305 segment is interesting. Amateur radio is secondary, but there is no primary user. My guess is that it's kept this way to provide a guard band to the deep space band at 2290 to 2300 MHz.
An alternative frequency would be 2395 MHz, but that's very close to the WiFi band. If you really want to be stealth, then 10 and 24 GHz would be ideal.
This "problem" (TCP over HF/VHF) has been solved around 1979(sic!).
http://lea.hamradio.si/~s53mv/nbp/nbp.html
http://lea.hamradio.si/~s53mv/nbp/new.html (10mbits over ~100km)
In most european countries, getting a ham licence is a pretty cheap process (in slovenia, in some radio clubs, if you don't need a printed book (just a pdf), you can join a 10-15hour theoretical and practical course + licence exam for somewhere around 50eur)
Can something like this in practice be used with HAM radio via some loophole, or it's basically impossible to use a large fraction of commonly used protocols/payloads (https, ssh, any secured protocols, VPNs, etc) due to encryption not being allowed? I suppose you could argue that the intention is not to obscure the communication, but it seems pretty flimsy.
I know that some use WiFi outside normal bands (3.3–3.8 GHz) and simply set the SSID to their call sign. This is called HSMR.
Typical is in quotes because some people think it is cool to allow their radios to transmit up to 10KHz bandwidth because “high fidelity SSB” is apparently a thing.