247bf84fda

VPN NAT Service Forwarding HOWTO - DRAFT v0.1

This guide describes how to configure a VPN frontend server where incoming TCP IPv4 connections are forwarded over a VPN to services running on a remote backend server. All outgoing connections from these services are routed via this same VPN frontend. Lightning Network nodes are described but this approach should work for just about any TCP service.

Guards against the public easily ascertaining the location of the backend server.
LN payments require lower latency and higher reliabilty than Tor is consistently capable.
Unlike ssh port forwarding or proxy-based frontends the backend service is able to see the actual source IP address of incoming connections, and nobody ever sees connections coming from the backend's address.
Allows for DoS filtering measures to happen at an external service provider before traffic reaches your backend network.

bitcoin

How a cheap $5/mo VM can act as a VPN frontend to hide the physical location of your backend LN node | @wtogami

cointastical


> *VPN NAT Service Forwarding HOWTO - DRAFT v0.1*
>
> This guide describes how to configure a VPN frontend server where incoming TCP IPv4 connections are forwarded over a VPN to services running on a remote backend server. All outgoing connections from these services are routed via this same VPN frontend. Lightning Network nodes are described but this approach should work for just about any TCP service.

> Why would you want this?
>
> Guards against the public easily ascertaining the location of the backend server.
> LN payments require lower latency and higher reliabilty than Tor is consistently capable.
> Unlike ssh port forwarding or proxy-based frontends the backend service is able to see the actual source IP address of incoming connections, and nobody ever sees connections coming from the backend's address.
> Allows for DoS filtering measures to happen at an external service provider before traffic reaches your backend network.
