Reliability connectivity upgrade / gossipsub discovery

[notassigned]

No description provided.

[alecbcs]

@notassigned just booted up two virtual machines in order to test out the max bandwidth of hyprspace after this PR. Unfortunately, I can't seem to get the two systems to find each other through hyprspace after this PR. They seem to find each other using the traditional method but not through pubsub? Running hyprspace daemon up I'm only getting to the first print and then it's freezing. Any recommendations? Can you still get two nodes to communicate with this PR?

[notassigned]

Running hyprspace daemon up I'm only getting to the first print and then it's freezing. Any recommendations? Can you still get two nodes to communicate with this PR?

Hmm i wonder if its an issue with the root check, did you run it with sudo?

You should only have to start the daemon with root, hyprspace up x will work without sudo after the daemon is running.

[alecbcs]

Apologies I should have included it in my previous response but yes I ran both commands as the root user in the VM. hyprspace daemon up only ever prints out,

Starting hyprspace daemon on port 5882

I haven't seen a connected verification message and all pings between the two VMs fail with all packets lost.

Rolling back to the main branch they can connect and transfer data at about 258Mbps between them.

[notassigned]

Apologies I should have included it in my previous response but yes I ran both commands as the root user in the VM. hyprspace daemon up only ever prints out,

Starting hyprspace daemon on port 5882

I haven't seen a connected verification message and all pings between the two VMs fail with all packets lost.

Rolling back to the main branch they can connect and transfer data at about 258Mbps between them.

Just to be clear are you running hyprspace up interface after you run hyprspace daemon up. What is the output on the command line when you do hyprspace up interface? You should see [+] Started hyprspace interface <interface>