Wow ... judging from all of these harsh comments, it seems the flood from Reddit to HN is going "well". I cannot believe all of the negative comments around the development of a piece of handy software.
I Got Sick of Remembering Port Numbers
131–140 of 171 posts
Re: I Got Sick of Remembering Port Numbers
#132Earlier quoted context omitted.
> ipv6 packet does not have any port field Yes, that's why I said I know it was mixing of layers. However ports are a layer violation in a strict sense, introduced as a workaround because there was no easy way to just add thousands of new IPs to a single host back in the IPv4 days. No need to continue a workaround that causes grief on a daily basis.
What do you mean? You’ll still have to use TCP or UDP over IPv6, and both of those protocols use ports. Nothing is stopping you from creating a transport protocol that doesn’t use ports if you want to, but that has nothing to do with the network layer.
I mean that to connect to a service you wouldn't need to know the port, the IPv6 address would be enough.
This is why I consider ports a layer violation of sorts. You never talk to a machine with TCP/UDP, you talk to a service on a machine. And so as it is the full address to the service isn't just the layer 3 address.
As I mentioned this would be especially interesting when hosting multiple services, same or different, on the same machine since there would be no port conflict.
Re: I Got Sick of Remembering Port Numbers
#133I have a strange short-term memory that immediately forgets where I was. I think it just decides I made my decision and no longer needed that trivia clouding the next thought. This is exactly what I have struggled with. Thanks a ton for this!!
Re: I Got Sick of Remembering Port Numbers
#134It 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?
Chinese spyware.
https://www.reddit.com/r/msp/comments/1pxe1zc/tplink_ban_pro...
https://www.pcmag.com/news/facing-router-ban-tp-link-tells-f...
https://www.nytimes.com/wirecutter/reviews/foreign-made-wi-f...
Just search for "TP Link ban", you will see a lot of news. I switched to SonicWall + Ubiquiti + my own monitoring software to be safe. I should've done it years ago, but I was lazy.
Re: I Got Sick of Remembering Port Numbers
#135Earlier quoted context omitted.
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…
Sounds like you need an AI agent that can determine whether http and gopher are the same protocol
Re: I Got Sick of Remembering Port Numbers
#136It'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...
The best way to find the right answer on the Internet is to slop-code a half-assed solution to a long-solved problem.
https://meta.wikimedia.org/wiki/Cunningham%27s_Law
Sidenote: A good AI would interject, Clippy-like, "It looks like you're trying to recreate /etc/services. Would you like me to explain what that is?"
Re: I Got Sick of Remembering Port Numbers
#137Earlier quoted context omitted.
As bandie pointed out, you‘re explicitly making a http request. Duh. nc is for generic connections and handles it well.
i know, but the OP's goal was to host/access http(s) services with names and avoid port numbers, and gopher service name was chosen by me as an example. my point was that /etc/services cannot be used for the OP's need. if you host an http(s) service on port 11111 you can reach it with url http://127.1:11111 , but url http://127.1:vce/ would not work in most software. $ grep 11111 /etc/services vce 11111/udp # Viral C…
If I curl my phone number it doesn't connect, that's strange
Re: I Got Sick of Remembering Port Numbers
#138People will do anything to avoid learning the basics. Nothing new.
Do you have a link for me? I'd like to learn them, but find it really hard to find them.
For example, I had never heard about etc/services until 2 minutes ago
Re: I Got Sick of Remembering Port Numbers
#139Wow ... judging from all of these harsh comments, it seems the flood from Reddit to HN is going "well". I cannot believe all of the negative comments around the development of a piece of handy software.
I mean, it’s the shitty human nature. You can't create anything publicly without people bashing your project, and you, for the sheer insolence of creating a piece of software.
Re: I Got Sick of Remembering Port Numbers
#140Don't use localhost:3000, use your own custom domain[0]
0. https://idiallo.com/blog/say-no-to-localhost3000-use-custom-...