p2p-vpn for PVV hosts? #168

Open
opened 2024-10-31 15:34:34 +01:00 by pederbs · 1 comment
Owner

The loss of public IP addresses, volatile server racks, labnets, etc, is a threat to PVVs continued server operations. Do we want to risk a frownyface and set up a mesh/p2p-vpn for pvv machines?

If yes:

  • We have to decide which OSes to support:
    • freebsd
    • linux
    • macos
    • windows
  • If we want NAT-traversal
  • If we want to self-host the broker/entry point (i.e. headscale)
  • Which mesh-VPN provider to use:
    • Zerotier
    • Mycellium
    • Tailscale
    • lol let's just raw-dog wireguard
  • What requirements/rules to apply to hosts to enter the mesh
The loss of public IP addresses, volatile server racks, labnets, etc, is a threat to PVVs continued server operations. Do we want to risk a frownyface and set up a mesh/p2p-vpn for pvv machines? If yes: * We have to decide which OSes to support: * [ ] freebsd * [ ] linux * [ ] macos * [ ] windows * If we want NAT-traversal * If we want to self-host the broker/entry point (i.e. headscale) * Which mesh-VPN provider to use: * Zerotier * Mycellium * Tailscale * lol let's just raw-dog wireguard * What requirements/rules to apply to hosts to enter the mesh
pederbs added this to the Kanban project 2024-10-31 15:34:34 +01:00
Owner

Prior art: #52

vi har også prøvd noen pga. det prosjektet der

Prior art: #52 vi har også prøvd noen pga. det prosjektet der
oysteikt added the
new stuff
services
labels 2024-12-08 00:52:55 +01:00
Sign in to join this conversation.
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: Drift/issues#168
No description provided.