Hmm. Not sure what you mean exactly then, my apologies. It's not exactly mapping, you just tell your program what port to listen on. If you tell it to listen on 80 and point a web browser to localhost, your web browser will then be talking with your program.
-
-
Replying to @PlainOldWaffles @BerzerkerBuilds
Yes I know that but what does the 80 *do* that 79 *doesn’t*
1 reply 0 retweets 0 likes -
Replying to @EmilyGorcenski @BerzerkerBuilds
Absolutely nothing :) That's the beauty. Ever use a web browser to connect to your home router on port 8080? Functionally identical to Port 80, they just use 8080 so as not to conflict with anything listening on 80
2 replies 0 retweets 0 likes -
The port numbers themselves are meaningless. There are standard ports. Like again 80 and 443, etc. But ANY program can take over that port and do it's own thing. It's not the port that determines the protocol
1 reply 0 retweets 0 likes -
Replying to @PlainOldWaffles @BerzerkerBuilds
Lemme phrase it like this: # If I expose only port 4500 on a host, and try to send a request on 4600, I will get no response. Where does the machinery lie that allows the host to ignore the request on 4600?
1 reply 0 retweets 0 likes -
Replying to @EmilyGorcenski @BerzerkerBuilds
You have to have some program running on that PC that opens a listening socket on any given port. Then that program literally just sits there running waiting for something to connect in that port. If you don't have any server programs running, there won't be any ports listening
2 replies 0 retweets 0 likes -
Replying to @PlainOldWaffles @BerzerkerBuilds
How does the server software know to reject a request coming in on a port that’s not open. Is the port number encoded in the packet?etc. Again, I know what ports are but not how they get implemented on the transport layer
3 replies 0 retweets 0 likes -
Replying to @EmilyGorcenski @BerzerkerBuilds
Oh hell, if you're talking about packet headers, that's getting into the weeds there :) Wireshark can capture raw packets and show you exactly what's in the headers (MAC, remote server, port, etc)
1 reply 0 retweets 0 likes -
Too late to start going into layer 2 / layer 3. And I'm no where near expert enough to explain that properly. But yes, all that stuff IS part of the packet, but you still have to open a socket. UDP however does not require a socket connection.
1 reply 0 retweets 0 likes -
UDP is just literally throwing shit at a wall and hoping something gets it. Doesn't care if it does or not. Good for gaming but unlike tcp/ip no guarantee that the packet got anywhere. Tcp/ip has built in acknowledgment to confirm the other side received the last packet
1 reply 0 retweets 0 likes
Yes I know that
-
-
Replying to @EmilyGorcenski @BerzerkerBuilds
It sounds like you might be asking about WinSock. Sorry, if I was totally off on the wrong thing therehttps://searchwindowsserver.techtarget.com/definition/Winsock …
0 replies 0 retweets 0 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.