It 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 Got Sick of Remembering Port Numbers
21–30 of 171 posts
Re: I Got Sick of Remembering Port Numbers
#22[dead]
Re: I Got Sick of Remembering Port Numbers
#23Why not resolve everything with UNIX sockets instead, that way you can have them named and scoped instead, hiding behind port 443, since it's mosly HTTP anyway.
Re: I Got Sick of Remembering Port Numbers
#24I 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 number.
Re: I Got Sick of Remembering Port Numbers
#25Re: I Got Sick of Remembering Port Numbers
#26What is the benefit of using HTTPS for this particular use case?
Re: I Got Sick of Remembering Port Numbers
#27Why not resolve everything with UNIX sockets instead, that way you can have them named and scoped instead, hiding behind port 443, since it's mosly HTTP anyway.
Does this work in the browser? How will paths to different resources used by the web app work?
Re: I Got Sick of Remembering Port Numbers
#28Vercel’s portless is a great alternative, but unfortunately it doesn’t work well with oauth flows.
I’ve built portmap[0] to solve that. Also comes with skills which makes it work really great with coding agents (instructions in the readme).
Re: I Got Sick of Remembering Port Numbers
#29I wonder why not use nginx and some local DNS settings to just serve all these local services under a new, local URL.
Not too long ago I had a similar issue and solved with that.
Re: I Got Sick of Remembering Port Numbers
#30It'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...
And then they might code up some sort of service lookup tool thingy to use on the train wreck that is the modern web. $ getent services gopher gopher 70/tcp
this is a nice idea, but
idk why, in macos if i do
`nc -l 127.0.0.1 gopher`
and then try to open url "http://127.0.0.1:gopher/" - safari does not open it, no requests visible in the `nc` output.
also `curl -v http://127.0.0.1:gopher/` gives error message
* URL rejected: Port number was not a decimal number between 0 and 65535
* Closing connection
curl: (3) URL rejected: Port number was not a decimal number between 0 and 65535