4 ms·
> have each service that deserves to be reached over the listen on an address unique to the service It’s already a thing. These unique per-service addresses ar
by nlitened 2y ago
> have each service that deserves to be reached over the listen on an address unique to the service
It’s already a thing. These unique per-service addresses are called “ports” in IP protocol.
- deleted 2y ago[deleted]
- eptcyka 2y agoHosting service A shouldn't mean that every user of service A can also figure out you host C, B and D. Also, the IP protocol does not care about ports at all. Ports are a thing for UDP and TCP.
- nlitened 2y ago> Also, the IP protocol does not care about ports at all. Ports are a thing for UDP and TCP. You're right, they are one level above. > Hosting service A shouldn't mean that every user of service A can also figure out you host C, B and D. It how are ports on a single IP address essentially different from multiple IP addresses within a subnet?
- eptcyka 2y agoIn a /64, enumerating all hosts will not be as practical as enumerating all ports on a single IP. Further, you will not be able to link that two services are running on the same host by just the IP.