diff options
Diffstat (limited to 'content/posts')
| -rw-r--r-- | content/posts/openbsd-vpn-gateway/index.org | 57 |
1 files changed, 33 insertions, 24 deletions
diff --git a/content/posts/openbsd-vpn-gateway/index.org b/content/posts/openbsd-vpn-gateway/index.org index c8005e5..997f049 100644 --- a/content/posts/openbsd-vpn-gateway/index.org +++ b/content/posts/openbsd-vpn-gateway/index.org @@ -412,30 +412,39 @@ various config options, but I won't go through that here to keep this section somewhat brief. - On OpenBSD, if we have a static IP setup on our OpenBSD machine, - like we did as part of this tutorial, it's as simple as replacing - the contents of =/etc/mygate= with the IP of our new VPN gateway, - and then either running ~doas sh /etc/netstart~ or rebooting. This - is covered more in depth on the [[https://www.openbsd.org/faq/faq6.html][OpenBSD FAQ]]. +** OpenBSD + On OpenBSD, if we have a static IP setup on our OpenBSD machine, + like we did as part of this tutorial, it's as simple as replacing + the contents of =/etc/mygate= with the IP of our new VPN gateway, + and then either running ~doas sh /etc/netstart~ or rebooting. This + is covered more in depth on the [[https://www.openbsd.org/faq/faq6.html][OpenBSD FAQ]]. - FreeBSD's [[https://www.freebsd.org/doc/handbook/config-network-setup.html][handbook]] covers this topic very well. The basic steps are: - - Add a line ~ifconfig_<if>="inet - - Most graphical interfaces for Linux desktop environments will have a - networking section that will allow you to set the gateway without - too much fuss. [[https://linuxconfig.org/how-to-configure-static-ip-address-on-ubuntu-20-04-focal-fossa-desktop-server][Here]]'s a walk through from https://linuxconfig.org. - - The situation for Linux servers is a bit more of a mess. As covered - in the previously linked article, Ubuntu now likes to use the - =netplan= framework, while others like Fedora may prefer =nmcli= as - stated in [[https://linuxconfig.org/how-to-configure-static-ip-address-on-fedora-31][this]] article, or =network-scripts= as states [[https://www.systutorials.com/how-to-set-the-static-ip-address-using-cli-in-fedoracentos-linux/][here]]. If you - take this path it's recommended you look into how it should be done - on your specific Linux distribution. - - Most graphical +** FreeBSD + FreeBSD's [[https://www.freebsd.org/doc/handbook/config-network-setup.html][handbook]] covers this topic very well. The basic steps are + involve adding the following lines to your =/etc/rc.conf=: + - ~ifconfig_<if>="inet XXX.XXX.XXX.XXX netmask YYY.YYY.YYY.YYY~, + where =<if>= is the interface, and =X= and =Y= are your IP and + netmask. + - ~defaultrouter=<gateway_IP>~ where =<gateway_IP= is the gateway's IP + - ~nameserver ZZZ.ZZZ.ZZZ.ZZZ~ where =Z= is the DNS IP. ** Linux - -*** Docker -** FreeBSD -*** Jails + Most graphical interfaces for Linux desktop environments will have a + networking section that will allow you to set the gateway without + too much fuss. [[https://linuxconfig.org/how-to-configure-static-ip-address-on-ubuntu-20-04-focal-fossa-desktop-server][Here]]'s a walk through from https://linuxconfig.org. + + The situation for Linux servers is a bit more of a mess. As covered + in the previously linked article, Ubuntu now likes to use the + =netplan= framework, while others like Fedora may prefer =nmcli= as + stated in [[https://linuxconfig.org/how-to-configure-static-ip-address-on-fedora-31][this]] article, or =network-scripts= as states [[https://www.systutorials.com/how-to-set-the-static-ip-address-using-cli-in-fedoracentos-linux/][here]]. If you + take this path it's recommended you look into how it should be done + on your specific Linux distribution. + +** Containers/Jails + Most graphical LXC container or Jail host software like [[https://www.proxmox.com/en/proxmox-ve][Proxmox-VE]] + or [[https://www.freenas.org/][FreeNAS]] should have a fairly obvious place to put the IP when + setting up the containers/jails. + + Otherwise you may want to consult the documentation of the + container/jail management software you may be using (docker, + iocage, etc.) |