New answers tagged

0

the Client starts the connection so the server has to respond to the "faults" either of the network or the client himself. To handle this the Server gives the client a timeout before a RST (reset) get send and the connection gets closed from server side. If the client wants to close the connection he would send a FIN to signal he has nothing more ...


0

The timers and sequence numbers are for the reliability that TCP gives, not really anything to do with security. See RFC 793, Transmission Control Protocol: When the TCP transmits a segment containing data, it puts a copy on a retransmission queue and starts a timer; when the acknowledgment for that data is received, the segment is deleted from the queue. ...


0

Transport layer protocol means a protocol that actualy conveys data by encapsulating it and providing means for securing it or acknowledging it for exemple which is not the case with what icmp does. In addition,it is integrated in every IP layer implementation (wether on end host or networking device) so you can even say it works in conjunction with ip ...


2

We know that port 80 is just a welcoming port, when the web server reveives a http request, it create a new connection port(let's say 5000) No, that's not true. Port 80 is the destination port that all packets send to the web server's web service are sent to. So my understanding is, the initial address of the client uses to send packet to the the server's ...


0

As EIGRP is interior gateway protocol . EIGRP algorithm is designed in such a way that EIGRP with same atonomous number . EIGRP router will speak to another router which is in same atonomous system number .


9

We know that port 80 is just a welcoming port, when the web server reveives a http request, it create a new connection port(let's say 5000) That's not correct for the HTTP protocol. Some protocols, namely FTP, work similarly to that, but not HTTP. So my understanding is, the initial address of the client uses to send packet to the the server's ip address + ...


6

We know that port 80 is just a welcoming port, when the web server reveives a http request, it create a new connection port(let's say 5000) This seems to be the source of your misunderstanding. This is not accurate. The client picks a random high-number port as the source port when making the connection. This happens before the TCP SYN packet is sent, so it ...


3

No ,! Server destination port never changes its remain same in your scenario it's http port 80 . Application is hosted on port80 and services are listening on port 80 at destination server . When client requests accessing webserver on port 80 client will generate a souce port as per your example it is port 5000 and destination port is port 80 and port ...


15

No, a TCP connection is uniquely identified by both source and destination IP and TCP (port) addresses. Changing any one of those will break the TCP connection (or prevent it from forming in the handshake). What you may be referring to is the fact that a web browser will form, use, and close multiple TCP connections with the web server. Each connection will ...


Top 50 recent answers are included