For a brief status of the established connections, execute:
sudo husarnet status
The output will look like this:
Husarnet IP address: fc94:7196:e39f:23ff:fe45:81aa:39e4:b224 UDP connection to base: [::ffff:184.108.40.206]:5582 Peer fc94:9e5d:fef0:7bb4:00f1:fcb7:d85:fdaf tunelled secure connection established Peer fc94:a2e4:7b6b:322b:b200:97fa:e32f:a867 target=[::ffff:10.0.0.15]:5582 secure connection established
Let's analyse this information.
The second line contains information about connection to the base server. Base server helps devices find each other over the internet.
UDP connection to base: [::ffff:220.127.116.11]:5582
Normally, you should see information about successful UDP connection.
WARN: only TCP connection to base established
If there is only TCP connection established, you won't be able to establish direct connection to other devices over the internet. The data will be tunnelled over the base server - this will negatively impact latency and performance.
In order to fix this, unblock UDP on the firewall. You need at least UDP port 5582, but it's recommended to allow all outgoing connections.
ERROR: no base connection
This message means that most likely there is no internet connection. You will be only to contact devices in your local network.
Important: Make sure to ping the peer before checking its information in
husarnet status - it is only updated when communication is attempted.
Peer fcXX:YYY section contains information about connection to a specific peer.
If the second line contains
tunnelled, that means that you have no direct connection to the peer - this negatively impacts latency and performance. This is most likely caused by restrictive firewall or symmetric NAT. Here are some tips on how to fix it:
conntrack -Fon Linux router or virtual machine host
Otherwise, there will be a line containing
target=XXXX, where XXXX is the internet address used for communication with this node.
Hostnames of the devices in Husarnet network are stored in
/etc/hosts in lines with
# managed by Husarnet comment. They are modified automatically by the Husarnet daemon.
If you still have problems, you can report the problem by sending mail to
firstname.lastname@example.org. Please describe your problem and attach Husarnet log. You can retrieve the log using the following command:
sudo journalctl --unit husarnet > log.txt
The log will be saved as
log.txt in the current directory.
You can also report bugs on the public community forum.