varia/homebrewserver.club
14
0
Fork 0
Code Issues 1 Pull Requests Releases Activity

fix broken links, spelling

Browse Source
This commit is contained in:
rra 2019-09-24 10:37:19 +02:00
parent d0efeee910
commit ac30c599b1
2 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
content/fundamentals/intro.md
View File

@ -8,4 +8,4 @@ Status: published
Category: fundamentals Category: fundamentals
slug: 001 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)

4
content/fundamentals/port_forwarding.md
View File

@ -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. Summary: How to make your homebrew server reachable over the internet using your home router.
Author: hbsc & friends Author: hbsc & friends
Image: images/port_forwarding.svg Image: images/port_forwarding.svg
Status: draft Status: Published
slug: 005 slug: 005
[TOC] [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. 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) ![]({attach}images/ethernetcable.svg)