Hacker News new | past | comments | ask | show | jobs | submit login
Show HN: Hyprspace – A WireGuard Inspired VPN Built on Libp2p (github.com/hyprspace)
20 points by alecbcs 10 days ago | hide | past | favorite | 5 comments





Does it allow two devices, both behind NAT and without a public IP, to connect to each other?

Does it rely on some kind of central server that allows devices to discover each other?


> Does it allow two devices, both behind NAT and without a public IP, to connect to each other?

It does! This is one of the big differences between it and something like Wireguard. It uses NAT hole punching to create direct links between machines without any manual configuration.

> Does it rely on some kind of central server that allows devices to discover each other?

Sort of? When you first boot up your first two nodes it uses a set of "bootstrap peers" hosted by the IPFS team. These bootstrap peers allow instances to initially connect to and share their locations with other hyprspace instances with the same discovery key. Although we use these peers for discovery, none of your data is ever sent through them. All of the connections hyperspace makes at the moment are direct end-to-end encrypted peer-to-peer connections.


That's great, but what I'm interested in is, what happens if those boostrap peers are somehow blocked or unavailable? Can we be sure that have 100% uptime?

Can we host our own bootstrap peer and point our hyprspace clients to use that?

If not, then how is it different from ZeroToer?


Wireguard.com

Out of curiosity, how does this compare to ZeroTier?



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: