From 3439fce5f745bd0ea4fe41747afe8c6010e108c6 Mon Sep 17 00:00:00 2001 From: Austin Adams Date: Sat, 12 Sep 2015 12:11:32 -0400 Subject: vpn-ns doesn't create namespaces, so fix guide --- openvpn-example.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/openvpn-example.md b/openvpn-example.md index 9879ed8..968cf57 100644 --- a/openvpn-example.md +++ b/openvpn-example.md @@ -62,9 +62,9 @@ from my [openvpn configuration file][4]: script-security 2 Using [Sebastian's script][1] as a basis, I hacked together the -following. Notice that it uses iproute2 to create a network namespace -with the name of the instance's configuration file (`foo` in the earlier -example). +following. Notice that it guesses the name of the network namespace +based on the name of the instance's configuration file (e.g., +`/etc/openvpn/foo.conf`→`foo`). #!/bin/bash # based heavily on http://naju.se/articles/openvpn-netns -- cgit v1.0-2-geb64