From ac30c599b180e4a814d772693646c0b80d01e411 Mon Sep 17 00:00:00 2001 From: rra Date: Tue, 24 Sep 2019 10:37:19 +0200 Subject: [PATCH] fix broken links, spelling --- content/fundamentals/intro.md | 2 +- content/fundamentals/port_forwarding.md | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/content/fundamentals/intro.md b/content/fundamentals/intro.md index ab6cf56..2913cd4 100644 --- a/content/fundamentals/intro.md +++ b/content/fundamentals/intro.md @@ -8,4 +8,4 @@ Status: published Category: fundamentals slug: 001 -This series is a starting point for people looking to host their own on-line services from home. A good place to start is by reading the [homebrewserver.club principles]({filename}manifesto.md) on to understand why we make the choices we do. Then have a look at the [hardware guide](hwguide) or [setting up a server behind your home router.]({filename}portforwarding.md) +This series is a starting point for people looking to host their own on-line services from home. A good place to start is by reading the [homebrewserver.club principles]({filename}manifesto.md) to understand what the homebrew servers are about and how we make the choices we do. Then have a look at the [hardware guide]({filename}/hardware.md) or [setting up a server behind your home router.]({filename}portforwarding.md) diff --git a/content/fundamentals/port_forwarding.md b/content/fundamentals/port_forwarding.md index 8286784..6354fbb 100644 --- a/content/fundamentals/port_forwarding.md +++ b/content/fundamentals/port_forwarding.md @@ -6,7 +6,7 @@ save_as: fundamentals-port-forwarding.html Summary: How to make your homebrew server reachable over the internet using your home router. Author: hbsc & friends Image: images/port_forwarding.svg -Status: draft +Status: Published slug: 005 [TOC] @@ -84,7 +84,7 @@ Use an ethernet cable to connect your home server to your router. In case that i Have a look at your router's interface again and look for the IP-address that your server was assigned. In this guide I'll assume it was 192.168.1.10. -Next try to find an option called "Static (DHCP) Lease" or "DHCP Binding" or something similar in your LAN view. Then make sure to assign your server a static DHCP lease. This will make sure that the server is always reachable under the same IP-addres. +Next try to find an option called "Static (DHCP) Lease" or "DHCP Binding" or something similar in your LAN view. Then make sure to assign your server a static DHCP lease. This will make sure that the server is always reachable under the same IP-address. ![]({attach}images/ethernetcable.svg)