Interesting.
I've been wanting something like this for local Dev, but I think more:
Per user DNS.
So if the process doing the lookup is my own then redirect to the named service.
I Got Sick of Remembering Port Numbers
81–90 of 171 posts
Re: I Got Sick of Remembering Port Numbers
#82*.localhost works btw https://datatracker.ietf.org/doc/html/rfc6761#section-6.3
[deleted]
Re: I Got Sick of Remembering Port Numbers
#83Re: I Got Sick of Remembering Port Numbers
#84It's like someone should make a file... maybe in /etc ... and put short names for services in it... maybe it could be called /etc/services...
Top reply, and clearly based on the article's title rather than its content, as are the follow-ups. You're making this site worse. The article is short; go read it then come back and delete.
[deleted]
Re: I Got Sick of Remembering Port Numbers
#85Earlier quoted context omitted.
Top reply, and clearly based on the article's title rather than its content, as are the follow-ups. You're making this site worse. The article is short; go read it then come back and delete.
[flagged]
you go and look in etc services for what is bound to port 5009. the article might not be the most useful but these comments are completely off the mark and stupid.
Re: I Got Sick of Remembering Port Numbers
#86The file /etc/services maps names to port numbers, like /etc/hosts does for hosts. E.g. "telnet localhost ssh" takes you to port 22 (not the default 23 for telnet). This works because /etc/services maps "ssh" to "22". If you're sick of remembering port numbers, create some entries in your /etc/services. Of course, only programs which use getservbyname to resolve port numbers will accept your names.
maintaining services files.
i dont know why people keep insiting on that file while there are perfectly fine commands to pull from your boxes what is holding what port.
that is all besides the point though if you look at what you should be doing and keeping all this information in some kind of asset management system from which you can deploy things (which is kinda what k8s and docker etc. try to do (miserably)).
unless you are binding stuff to random ports on random boxes there is no need to do any of it at runtime and you can just consult your bookkeeping (for which etc services lacks a lot of details to use...)
Re: I Got Sick of Remembering Port Numbers
#87Re: I Got Sick of Remembering Port Numbers
#88There's a simple method you can use with nginx and /etc/hosts, I wrote about it couple days ago [0]. I used it for an internal demo recently and realized that a new breed of devs have never seen a non localhost url run locally. [0]: https://idiallo.com/blog/say-no-to-localhost3000-use-custom-...
I essentially do this.
Super simple. (although I use rewrites at my dns layer for the whole local lan, but whatever)
It also solves issues my password manager has with multiple services on the one host but with different ports, but putting each on their own 2nd level domain.
Re: I Got Sick of Remembering Port Numbers
#89It is funny, I just built something like this last week and named it "Network". Additionally it scans for any type of data packages arriving at the SonicWall and sees if they are approved by me or not. I am paranoid after using TP Link at home like a dumbass.
I am very out of the loop. What is wrong with TP Link? What are the risks with it?
Re: I Got Sick of Remembering Port Numbers
#90I know it's mixing of layers, but I can't help but feel the IPv6 transition missed the boat when they didn't just get rid of ports in the process. They've changed so much else anyway. Want to run another webserver instance or whatever on your computer? Get the OS to allocate a new IP for it. Ports be damned. Could be implemented in a backwards compatible way by requiring all IPv6 TCP/UDP traffic to use a fixed port n…
Conceptually its doable on linux and ipv6. Have the listening program sit on that default port of 80.
Something involving socat, an any-IP / TCP routing rule, a VPS or other machine with a ipv6 /64 and plenty of duct-tape.
You'd get an application sitting on port 80 accessible via some unique ipv6 address (in the /64) on a tcp port 80. They needn't be the same port number but it would make it easier.