![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.ml/pictrs/image/q98XK4sKtw.png)
Static IPs handed out by your local router are not dependent on having a static IP from your ISP. You do not need one to have the other. You can always have static IPs on your local network.
Static IPs handed out by your local router are not dependent on having a static IP from your ISP. You do not need one to have the other. You can always have static IPs on your local network.
I’d certainly be interested in full details. This sounds like the best of all worlds of not needing to double reverse proxy, not hardcoding internal IPs in the config of a single reverse proxy on the VPS, and not losing the source IP.
Does this cause all traffic at the reverse proxy to appear to come from the source IP of your VPS or does it preserve the original source IP?
I’ve been working on setting up a similar setup myself and am trying to figure out specifically how to handle the forwarding on the VPS.
This will completely change so many standard designs, such as train loaders and unloaders. I’m really looking forward to v2.0 now!
I took the title from the link, which doesn’t exactly match the title on the page. That’s why one says 20 years and the other says 15 years.
If you
then you, almost by definition, are an advanced user.
A beginner should avoid these things, once you are far enough along to understand why you might want to replace one of these things, and form your own opinion on it, then go right ahead. But you’re no longer a beginner at that point.