Unable to Reach Assigned VM Since July 24

General
1

Hi ERC Team,

We are currently unable to connect to our assigned VM via ping. This issue started on Thursday (July 24) and has persisted since then.

Because of this, we were unable to configure or test anything during or after the Post ROS Test on Friday, and we’re concerned this will impact our preparation for the Payload Test.

What we’ve tried:

  • Tested from multiple computers (laptops and PC) across different networks (home and university)
  • Verified husarnet status → VM appears as active, tunnelled
  • Tried ping to the VM → 100% packet loss
  • We can ping other teammates’ machines via Husarnet from the same setup
  • Used traceroute -6 → no response
  • Reinstalled both stable and nightly versions of Husarnet

Here is a screenshot showing that ping works perfectly with other devices, but not with the VM:

PROBLEM
PROBLEM1714×1460 118 KB

Clean Reinstallation Process

To eliminate any possible local issues, we decided to completely uninstall Husarnet and remove all associated files and configurations. We suspected there might be corrupted data or residual configurations affecting connectivity.

We then performed a full reinstallation using the nightly version, following the script below:

# FRESH ‑WIPE & INSTALL NIGHTLY (beta)

sudo systemctl stop husarnet 2>/dev/null || true
sudo systemctl disable husarnet 2>/dev/null || true
sudo apt-get remove --purge -y husarnet
sudo apt-get autoremove -y
sudo rm -rf /etc/husarnet /var/lib/husarnet /etc/default/husarnet
sudo rm -f /usr/bin/husarnet /usr/sbin/husarnet-daemon
sudo rm -f /etc/systemd/system/husarnet.service
sudo rm -f /etc/apt/sources.list.d/husarnet.list /usr/share/keyrings/husarnet.gpg
sudo rm -f /var/lib/apt/lists/install.husarnet.com_* \
            /var/lib/apt/lists/nightly.husarnet.com_* \
            /var/cache/apt/archives/husarnet_*_amd64.deb
sudo apt update
sudo apt clean
sudo systemctl daemon-reload

# Install nightly version
curl -s https://nightly.husarnet.com/install.sh | sudo bash -
echo "HUSARNET_INSTANCE_FQDN=beta.husarnet.com" | sudo tee /etc/default/husarnet > /dev/null
sudo systemctl restart husarnet
sudo husarnet join patrick.echevarria.d@gmail.com/<JOIN_CODE>
husarnet status

After this, husarnet status shows all peers, including the VM as active, tunnelled and healthy, however, the VM is still not accessible via ping even though it appears to be connected.

However, we suspect that the VM’s IP address may have changed, or there could be a connectivity issue such as a firewall blocking traffic or the VM being inactive internally. Even though it still appears as active and tunnelled in the Husarnet dashboard, it might not be functioning correctly or reachable over the network.

We kindly request your support in checking the current state and connectivity of the VM, as we are currently blocked from doing anything due to lack of access.

Thank you,
Team TerraBots

2

Hello Patrick,

Can you ping husarion-ops ? Or is it acting the same as team-70-terrabots ? (non-reachable)?

Your VM is running and I can reach it from my machine via Husarnet, so that definitely works.

I think that this is strictly tunneling problem; somehow packets are not routed correctly through the relay (base) server. I will look into this soon

BR,
Szymon

1 Like
3

Hello Szymon,

Thank you for your response.

No, we are also unable to ping husarion-ops, it behaves the same as team-70-terrabots (non-reachable). We agree that this seems related to tunneling or packet routing through the relay server.

We appreciate your help and will wait for your update.

Best regards,
TerraBots

4

Hello Patrick,
can you try again, we changed a few things
(please try using both stable and nightly versions of Husarnet)

BR,
Szymon

5

Hello Szymon.

We can now connect to the VM.

Thank you for your help.

Best regards,
TerraBots

1 Like