Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| sailing:networksetup [2023/11/29 15:11] – willy | sailing:networksetup [2024/02/22 08:44] (current) – removed willy | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | Next to: [[sailing: | ||
| - | Prev to: [[sailing: | ||
| - | ---- | ||
| - | |||
| - | ==== Networking Setup ==== | ||
| - | |||
| - | Your network configuration will be very important, and your set-up will determine lots of stuff specially from reverse-proxy and accessibility. There are a lot of different configurations, | ||
| - | |||
| - | So i have a flat home-network (1 subnet) with one upstream connection (ISP provider) that offers a private IP address and zero port-forwarding capabilties at all. I will get a bit more in details: | ||
| - | |||
| - | Flat home network: subnet 192.168.0.0/ | ||
| - | ISP provider with private IP (like over 4G or 5G, or some fiber ISPs too) that prevent you from using any DynDNS services | ||
| - | No port forwarding at all, even if the ISP router do provide a "port forward" | ||
| - | |||
| - | If you are, like me, in this situation you really don't have much choice. You can still obtain remote access if you have access to some kind of public IP like a VPS or if you can lease/ | ||
| - | |||
| - | |||
| - | |||
| - | ---- | ||
| - | Next to: [[sailing: | ||
| - | |||
| - | Prev to: [[sailing: | ||