Testing HulyNet
HulyNet is an internet within the Internet, and this is its testers’ manual: how to connect your computer, check that it works, and tell us how it went.
Once connected, your computer sends all of its Internet traffic through HulyNet. Each connection leaves HulyNet where it is served best: today a site in Russia is reached from Russia, and the rest of the Internet from another country. So what your own connection does not reach opens, and a service that serves only its own country still does. A site sees HulyNet’s address, not yours. The names of the sites you open are looked up inside HulyNet too, so your provider neither sees them nor answers them. If the connection breaks, nothing leaks: your computer has no Internet until the connection is back or you stop HulyNet.
This is a test version. We ask you to install it, use your computer as usual for a few days, and tell us how it went: whether it connects from your networks (home, mobile, work, public Wi-Fi), how fast it is, what breaks and when, and how long it stays up. A failed attempt helps us as much as a working one.
How HulyNet differs from other tools you may know, and why it has no file to import: the comparison.
1 Before you start
- Your decision. A tool that carries your traffic through another country may be unwelcome where you live. Decide for yourself whether to test, and stop whenever you want.
- What someone watching your connection sees: that your computer talks to HulyNet’s routers, in Russia and outside it (their addresses, and our server’s name), and how much data goes back and forth. They do not see which sites you open or what you send. The traffic is encrypted, but not yet disguised as ordinary browsing.
- What we see: your computer’s ID (the public half of a key HulyNet makes on it), its name with us, the addresses it connects from, and how much traffic it sends. Our routers carry your traffic, so, like any provider’s routers, they see which sites it goes to, but not the contents of encrypted (HTTPS) pages. They look up the sites’ names for you, and can reach your computer at its address in HulyNet. No other tester’s computer can reach it.
- You need the invite code from the testers’ chat. If you came here by its link, the code is filled in below already.
2 Install
One line installs HulyNet and connects your computer. It downloads HulyNet, checks it,
installs two programs, hulyscaled (the service) and hulyscale (the command you
use), starts the service, which starts again with the computer, and connects the
computer to HulyNet. When it says Done, your traffic goes through HulyNet.
Your computer gets a name, such as tester-7. To choose one yourself, add --name and
the name at the end of the line (on Windows, -Name), for example --name owl: up to
20 lowercase Latin letters, digits and -, starting with a letter, and nothing that
identifies you.
2.1 macOS
You need macOS 13 or newer, on Apple Silicon or Intel, and an administrator account. Open Terminal (in Applications → Utilities), paste this line, and press Return:
curl -fsSL https://hulynet.nothing.md/install.sh | sudo sh -s -- YOUR-CODE
Terminal asks for your Mac’s password: type it and press Return. Nothing appears while you type; that is normal. macOS reports Background Items Added: that is HulyNet, leave it allowed.
2.2 Linux
You need a 64-bit PC (x86_64 or ARM64) with a current distribution that uses systemd,
and sudo. For names to be looked up inside HulyNet, the system must use
systemd-resolved, as Ubuntu and its derivatives (Mint, Pop!_OS) and Fedora do:
resolvectl status prints your network’s settings if it does. On Debian, install
it first; your network keeps working, and names now go through it:
sudo apt install systemd-resolved
Other systems without it (Manjaro, say) cannot use HulyNet yet: please do not run the line there, it would take up a registration for nothing. The line, in a terminal:
curl -fsSL https://hulynet.nothing.md/install.sh | sudo sh -s -- YOUR-CODE
The service runs as root, because the system takes DNS settings only from root, and
keeps a single permission: managing the network. If the system cannot send its DNS
through HulyNet, HulyNet does not start its network: your traffic goes the ordinary
way, and curl https://ifconfig.me; echo prints your own address. journalctl -u hulyscaled says why. Once that is put right, run the line again: it keeps your
registration.
2.3 Windows
You need Windows 10 or 11 on a 64-bit PC (x64), and an administrator account. Windows on ARM does not work yet. Open a terminal as administrator: right-click the Start button, choose Terminal (Admin) (on Windows 10: Windows PowerShell (Admin)), and let it make changes. Paste this line and press Enter:
& ([scriptblock]::Create((irm https://hulynet.nothing.md/get.ps1))) YOUR-CODE
HulyNet goes to C:\Program Files\HulyNet, with Wintun, WireGuard’s network driver.
The hulyscale commands below need a terminal opened as administrator too, and a new
one after installing: the installer adds HulyNet to the path of new windows. Type them
without sudo.
3 Check that it works
curl https://ifconfig.me; echoprints HulyNet’s address, not yours. On Windows, typecurl.exe https://ifconfig.me: in PowerShell,curlalone is another command.- A site that your own connection does not reach opens.
- A DNS leak test (for example dnsleaktest.com) shows HulyNet’s address, not your provider’s servers.
hulyscale statussays which of our routers your computer is connected to,via entryorvia exit(more below), andfor all nameson itsdnsline.- Printers, shared folders and the other devices at home stay reachable: HulyNet lets your local network through.
4 How your computer chooses its router
Your computer connects to HulyNet at one of our routers, and chooses it by itself: the one that answers faster over a working connection. There is nothing to set.
- In Russia it is usually the entry, our router inside the country. The connection then stays inside the country, and your traffic travels on inside HulyNet. We expect a connection inside the country to be slowed down and interrupted less often than one that leaves it: that is what we want to test with you.
- Elsewhere it is usually the exit, our router outside Russia.
It moves to the other router only when that one has answered clearly faster for a couple of minutes, and it waits for a quiet moment, so that open connections are not cut. If its router stops answering, it moves at once.
Whichever router it is, your traffic leaves HulyNet the same way: to a site in Russia from Russia, to the rest of the Internet from the exit. So services that serve only Russian addresses open wherever you are: Russian Railways, Russian Post, Gosuslugi. Their names are looked up in Russia too, so a service that chooses its servers by where a name is asked gives the right ones.
hulyscale status says via entry or via exit, and on the next line why (by measurement). hulyscale peers shows that router with the path direct. If it says
relay, your traffic makes a detour through a relay of ours: send us a report.
5 Pause, stop, remove
sudo hulyscale stop # your own connection again
sudo hulyscale start # through HulyNet again
HulyNet also starts again with the computer. If it crashes, the system restarts it
within seconds, and in between you have no Internet: that is how nothing leaks. For the
same reason Windows may show No Internet for a few seconds right after it starts.
Whatever happened, sudo hulyscale stop gives you your own connection back.
To remove HulyNet from a Mac or from Linux:
curl -fsSL https://hulynet.nothing.md/install.sh | sudo sh -s -- --uninstall --purge
From Windows:
& ([scriptblock]::Create((irm https://hulynet.nothing.md/get.ps1))) -Uninstall -Purge
Without --purge (on Windows, -Purge), your computer’s key (its ID) stays, and a new
installation keeps its registration.
6 Tell us how it went
hulyscale report --private > hulyscale-report.txt
On Windows:
hulyscale report --private | Out-File -Encoding utf8 hulyscale-report.txt
Send us the file in the testers’ chat, with a few words:
- where you were: home, mobile, work, a café;
- what worked and what did not, and when it happened;
- if it got slow or stopped: roughly when.
7 If something goes wrong
- “This invite code is not valid”. Take the current one from the testers’ chat: each wave of testers gets its own.
- “The server takes no more testers”. Write to us in the chat.
- No Internet after HulyNet crashed. It restarts by itself within seconds: give it
half a minute. If it does not,
sudo hulyscale stopgives you your own connection back. hulyscale statussaysnetwork none. Run the install line again, with the code: it installs nothing twice and connects your computer again.hulyscale peersshows no connection to our routers. Send us a report: that is what we test.- Windows: “Access is denied”, or
hulyscaleis not recognized. Use a terminal opened as administrator, and a new one after installing. - Anything else: write to us in the testers’ chat.
8 Files, for installing by hand
The install line downloads the right one of these for your computer. Each archive
carries the configuration for this server. To install by hand, unpack it and run
sudo hulyscale/install.sh --system on a Mac, or sudo hulyscale/install.sh on Linux;
on Windows, in a terminal opened as administrator, powershell -ExecutionPolicy Bypass -File hulyscale\install.ps1 -Config hulyscale\hulyscale.toml. Then run the install line
with your code, which connects the computer.
| System | File |
|---|---|
| macOS 13 or newer, Apple Silicon and Intel | hulyscale-macos.tar.gz |
| Linux, x86_64 | hulyscale-linux-x86_64.tar.gz |
| Linux, ARM64 | hulyscale-linux-aarch64.tar.gz |
| Windows 10 and 11, x64 | hulyscale-windows-x86_64.zip |
Checksums: SHA256SUMS. The installers themselves: install.sh, and for Windows get.ps1.