I am genuinely curious as to what the mapping is between the integer value and the whatever under the hood.
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
-
-
It doesn't. It is only aware of the ports it's listening on. Everything else by default is just not opened. I guess think of it like a wall? By default no way to get through that wall. Something has to poke a hole through it? Terrible analogy ... :)
-
I know it’s like a wall. I’m asking what the wall is made of
End of conversation
New conversation -
-
-
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)
-
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.
-
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
-
Yes I know that
-
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 …
End of conversation
New conversation -
-
-
I think I'm side tracking. Sorry. It's late :) Hmm.i think I get what your asking now though. How does the "wall" know that something's listening on a port? Is a server telling a "wall" "hey, I'm here!" ?? I guess the wall could just be considered the WinSock libraries...hmmm
-
If your asking how the operating system brokers the server connection and the client connect, that I have no clue. From my perspective, it's so seamless I've never cared to find out. Server/client DO use built in libraries to create the sockets though.
End of conversation
New conversation -
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.