Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| sailing:networksetup [2023/11/30 07:10] – willy | sailing:networksetup [2024/02/22 08:44] (current) – removed willy | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | Prev to: [[sailing: | ||
| - | Next to: [[sailing: | ||
| - | ---- | ||
| - | |||
| - | ==== Networking Setup ==== | ||
| - | |||
| - | The network configuration is divided into two different parts: the home network and the remote access. The most complex part is being capable to remotely login to your home network because that requires the capability to actually reach your home network from outside some how. Back in the good days when you connected to the internet you where granted a public IP address that you could use to access your home network from outside. After some time, Internet Service Providers (ISPs) started giving you, more and more frequently, only a //private// ip address due to the well known scarcity of IPv4 address pool. This is much more common outside the U.S.A. and mostly common outside the western world. With mobile connections nowadays becoming quite common for the home connections (it's much cheaper to place a few 5G towers than to cable fiber everywhere) things are even worse than than. Luckily, at the same time, renting a VPS or a dedicated server with a public IP address is getting cheaper and easier. So there are always hopes for you. | ||
| - | |||
| - | ==== The Home Network ==== | ||
| - | Home networks are usually flat. This means you have no VLANs or managed Layer3 switches at home. You might have a //guest// network in addition to your main network (for the more advanced or privacy concerned of you) but that doesn' | ||
| - | |||
| - | I will assume your home network is on **192.168.0.0/ | ||
| - | * You **should** have a [[https:// | ||
| - | * You are connected to the internet using a router provided by your ISP at 192.168.0.254 | ||
| - | * Your server will have a static IP address set up as 192.168.0.1 | ||
| - | * The rest of your devices are on DHCP | ||
| - | |||
| - | Why static IP for your server? So that you can always reach it and you can easily set it's address to your devices without resorting to weird DNS setups or modifying your ISP (or Pi Hole) provided DHCP settings. | ||
| - | |||
| - | You should have already configured your network during the Gentoo installation, | ||
| - | |||
| - | I strongly suggest you use some better DNS settings than your own provider, since in many countries torrent sites and such might be filtered by laws. Edit your **/ | ||
| - | < | ||
| - | nameserver 8.8.8.8 | ||
| - | nameserver 8.8.8.4 | ||
| - | </ | ||
| - | |||
| - | (Note: be aware that if you use NetworkManager you need to set DNS within it's interface. The resolv.conf file will be overwritten) | ||
| - | |||
| - | to use Google' | ||
| - | |||
| - | ==== The Remote Access ==== | ||
| - | |||
| - | Remote accessing your home network can be an hassle. Let's see the most common options: | ||
| - | * Public IP address. Easiest: go get a DynDNS account of any kind and set it up in your ISP router, enable port-forwarding for your server or DMZ it, and you are all set. There are plenty of guides for this case, i will not get into more details. | ||
| - | * Private IP address, but with // | ||
| - | * Private IP address and no // | ||
| - | |||
| - | Well, you are in the worst possible condition and, let's be honest, there is NO way out unless you go down two different paths: | ||
| - | * Buy a VPN that provides port-forwarding. Avoid any VPN without port-forwarding. This is, again, easy but it's pricey and doesn' | ||
| - | * Rent (or access somehow) a server on the internet with a public static IP address. This is the best solution in my view (albeit probably more expensive than a VPN) because it opens a world of opportunities for you. | ||
| - | |||
| - | |||
| - | ---- | ||
| - | Next to: [[sailing: | ||
| - | |||
| - | Prev to: [[sailing: | ||