Why we built TunnelNet
We wanted our own IP addresses. Not borrowed from an internet provider, not tied to one line, not changing when the modem restarts. So we got our own, and built the plumbing to put them wherever we needed them.
Wanting an address of our own
Anyone who runs a server, a camera system or a lab at home or in a small office knows the problem. Your provider gives you an address, and it isn't really yours. It changes. It's shared with other customers behind CGNAT. Or there is a static IP plan, at an extra monthly price, on one line only.
MinakiLabs LLC took the long way round. We got our own network number (AS396500) and our own block of addresses (23.187.152.0/24), and we announce them to the internet ourselves. Then we built TunnelNet to carry those addresses over an encrypted tunnel to whatever machine needed one.
One machine first
That became TunnelNet Home: an address that's yours, on one computer or server, wherever it is plugged in. It doesn't matter what internet line is underneath. The tunnel goes out, so nothing has to come in through the provider's equipment.
Then the whole site
The same idea works one level up. Put the tunnel on the router instead of one machine, and the address belongs to the whole site. Every device behind the router can be reached on the ports you choose, and the router decides which internet line carries the tunnel. If the main line goes down and the router moves to the backup, the address goes with it.
That is TunnelNet Business. You still need a static IP, just not from your ISP. Ours doesn't care what's behind it.
Proving it on ourselves
We run our own office on it, and we write down what happens, including what breaks. Start with the field notes from our office, or the white paper for how it works and what we measured in our lab.