diff options
| -rw-r--r-- | content/posts/openbsd-vpn-gateway/index.org | 23 |
1 files changed, 14 insertions, 9 deletions
diff --git a/content/posts/openbsd-vpn-gateway/index.org b/content/posts/openbsd-vpn-gateway/index.org index 0ec91ec..0d4496e 100644 --- a/content/posts/openbsd-vpn-gateway/index.org +++ b/content/posts/openbsd-vpn-gateway/index.org @@ -19,15 +19,20 @@ * The Solution - The solution I came up with to this problem is to setup a VPN gateway - on my network using [[https://www.openbsd.org/faq/pf/][OpenBSD]]. Any device that sets that machine as it's - gateway will automatically get its traffic tunneled through the VPN - connection. It's also setup such that if the VPN connection ever drops - or gets killed for any reason, the traffic will stop and won't be able - to reach the internet. Thanks to this I don't have to worry about the - traffic ever leaking out through my residential gateway should OpenVPN - decide to close the connection. Sort of like a "kill switch", as some - companies market it. + The solution I came up with to this problem is to setup a VPN + gateway on my network using [[https://www.openbsd.org/faq/pf/][OpenBSD]]. Any device that sets that + machine as it's gateway will automatically get its traffic tunnelled + through the VPN connection. Because I'm setting the VPN up as a + second gateway on an existing network, all devices on the network + will still be able to talk to each other normally, regardless of + which gateway they use. + + It's also setup such that if the VPN connection ever drops or gets + killed for any reason, the traffic will stop and won't be able to + reach the internet. Thanks to this I don't have to worry about the + traffic ever leaking out through my residential gateway should + OpenVPN decide to close the connection. Sort of like a "kill + switch", as some companies market it. * Our Network |