I can’t believe it. You’re the only one that made me understand. Thank you!!!
@supersoniqamanyi3075
2 жыл бұрын
WOW!!! unbelievable how simple this is
@aaammm8206
Жыл бұрын
Hi mate, just wanted to thank you with the content! very helpful and much appreciated!
@cksuwarnaraj
7 ай бұрын
thank you
@acealmis1533
4 жыл бұрын
clearly explained. thanks a lot
@adamjacob5482
4 жыл бұрын
I will take it easy, thank you :)
@SchlonzKlug
4 жыл бұрын
Thanks for that. Super nice explained. How do apps distinguish between different apps when using same services? For example when I access the same web page with two different browser?
@oresteszoupanos
4 жыл бұрын
I think when you access the same webpage with 2 browsers, your computer can be using any 2 different ports which are then connected to the same remote host and port (usually port 80 for HTTP and port 443 for HTTPS). You can test this on your computer by opening your 2 browsers and then using a tool like Process Hacker to look at what network ports are being used by each browser.
@MrEric377
4 жыл бұрын
Oh, this is my understanding. TCP ports range from 1- 65535, but they are split up so to speak. Where ports 1 - 1023 are "reserved" for service / daemons. These reserved ports are 80 for http 443 for https, 22 for ssh and so on (Please google TCP ports for more ). When lets say host B is running a "secure" website it usually listens for traffic on TCP 443. When host A tries to establish a connection (Chrome lets say) it uses a different range of random / dynamic ports (I am not too sure about the range, but lets say 49152 to 65535) so host A will use dynamic port 49222 to host B on port 443. If you do establish more connections host A will simple use another dynamic port range (that is not already in use) but still connect on port 443 on host B. In windows you can use netstat / powershell cmd and I believe you can run netstat in Linux to see network connections.
@slimlowjack
4 жыл бұрын
The well known ports are the destination ports. Your PC will connect to port 22 on a server for SSH, but when that traffic is returned, it will be on one of the ephemeral ports (49152-65535). So, in this example, the source (your PC) will be port 55261 and the destination will be port 22 (Linux server). If you open a packet sniffer, you'll see something similar for web traffic. Its connecting to the web server on port 80 or port 443 but returning to your PC on one of the higher number ephemeral ports.
@loc4725
4 жыл бұрын
Lots of answers but I'll add my "2c". ☺ The transport layer uses tupples (related sets of data) to identify each unique connection. So on the client side it uses the client port, server port and server IP address to identify who owns a connection. Connect with a different web browser on the same machine? Well server port and server IP address will be the same but the *client port* will be different so the protocol stack knows who to pass that packet to. Similarly on the server side the client IP address and destination port (server port) will be the same but the source (client) port will be different, representing a unique connection to the same machine.
Пікірлер: 12