Today we will learn about loopback addresses that can be reached from the outside via routing. This is useful for running services on a router In a previous post, I talked about the loopback interface and how we can locally bind services to any address in the range 127.0.

Old article I found in my bookmarks. Although I didn’t have the use for it, I thought it was interesting.

  • PyrosisEnglish
    2•7 months ago

    I like to utilize nginx proxy manager alongside docker-ce and portainer-ce.

    This allows you to forward web traffic to a single internal NPM IP. As for setting up the service ips. I like to utilize the gateway ips that docker generates for each service.

    If you have docker running on the same internal IP as NPM you can directly configure the docker gateway ips for each service within the NPM web configuration.

    This dumps the associated traffic into the container network for another layer of isolation.

    This is a bit of an advanced configuration but it works well for my environment.

    I would just love some support for quic within NPM.