4 ms·
Using port number as a service identifier sucks because it means you can only run e.g. one normally-accessible SSH server per IP address. One potential solution
by oasisaimlessly 2y ago
Using port number as a service identifier sucks because it means you can only run e.g. one normally-accessible SSH server per IP address. One potential solution is to look up port numbers via DNS SRV records[1], but very few protocol standards demand clients do this.
HTTP and SMTP have their own ad-hoc, partial solutions to this (vhosting, MX records), but most every other service requires a unique IP address per instance.
* [1]: https://en.wikipedia.org/wiki/SRV_record https://en.wikipedia.org/wiki/SRV_record
- mistrial9 2y ago"How to Configure SSH for Multiple Ports | Baeldung on Linux March 18, 2024 - Learn how to start an SSH server on multiple ports."
- mmerlin 2y agohttps://www.baeldung.com/linux/ssh-multiple-ports https://www.baeldung.com/linux/ssh-multiple-ports
- akira2501 2y ago> one normally-accessible SSH server per IP address With IPv6 this consideration is almost completely moot. > MX records Have fun with your MX not being port 25. > but most every other service requires a unique IP address per instance. This constant engineering overhead to play to the weaknesses of IPv4 is the problem.
- bandie91 2y ago> Have fun with your MX not being port 25. why? it would be a great spam filter!