3 more flags added in TCP flags to notify the sender about Congestion in the Network. Please watch the Video till end to know more.ua-cam.com/video/k-0GLQV753I/v-deo.html&ab_channel=TechClout
URG is strongly discouraged (RFC9293). No point spending too much time explaining this never-really-working functionality. Nonce Sum has been obsoleted / made historic (rfc8311) You may want to update / enhance this talk with the Accurate ECN mechanism and the ACE field, as well as the AccECN handshake/negotation mechanism
Errate: ECE/CWR only has that semantic as explained while the SYN bit is set; the semantic changes during the actual data exchange. Also CWR is bit 8 and NS used to be bit 9 (wrong order). But that is now the AE flag. And the explanation of the CWR is completely incorrect as is the ECN mechanism. I hope everyone actually reads RFC3168 and doesn't take this as proper explanation. In short: Sender set's IP ECN to ECT(0) [on new data, not control, ACK, or retransmissions]. Congested Switch converts IP ECT(0) -> IP CE Receiver latches ECE flag on the returned ACKs (reliable feedback of the IP CE codepoint, but only one CE per RTT possible) Sender observes ECE, reduces congestion window as per the congestion algorithm and sends - on the next new data packet - CWR once. Receiver clears the latched ECE once the CWR arrives - for about a decade most stacks had a bug, where a CE-marked CWR packet would *not* latch ECE on immediately again, btw. It would be nice to redo this video (and remove the old version).
Unfortunately, for the ECE, CWR, and NS part, it was also mostly entirely wrong. Spending time on URG was pointless as noone really uses/implements this any more.
The Push flag explanation isn't correct. The Push flag itself means that push the data immediately to the application layer without being waiting for the entire segment to get filled. The Push flag indicates that you don't to wait anymore this is what is the end and you should send the segment ASAP to the upper layer. The Urgent flag prioritize the data over other data. If there are multiple segments in the buffer and one of the segment has the pointer set then it will be processed first over the other segments. Now if you have one segment with URG pointer set and other with Push, then obviously the URG will be prioritized first. Thanks!
once you push data on a connection you have to wait for the receiver to get all of it before it gets to the new data. This is where the URG flag kicks in. When you send urgent data, your TCP creates a special segment in which it sets the URG flag and also the urgent pointer field. This is what I got from the internet. I think he correct in video
Jeremy Stretch has a good write-up about it please read about it on internet. So now the telnet is connecting to a remote computer, we want to be able to have the commands we type executed right after we typed them. That is why they are flagged with URG flag.
Thankyou for Asking and sorry for replying late. So Xmas flag is nothing but a term being used to identify a kind of attack. In which attacker turn on three important flags( SYN, URG & PUSH) which make the destination device busy or over load it to stop processing the legitimate traffic. You can find this if you have any wireshark capture for DDOS attack.
sir the difference between push and urgent flags as u mentioned is totally wrong ...u need to check it again because u just tell the opposite ...sir telnet uses push not urgent sir please think about it
Thankyou for you query-:) Because telnet is connecting to a remote computer, we want to be able to have the commands we type executed right after we typed them. That is why they are flagged with URG flag. I hope this clear you.
![TCP and the Three-Way Handshake Explained [Follow-Along Lab] 🚀](/img/n.gif)
3 more flags added in TCP flags to notify the sender about Congestion in the Network. Please watch the Video till end to know more.ua-cam.com/video/k-0GLQV753I/v-deo.html&ab_channel=TechClout
URG is strongly discouraged (RFC9293). No point spending too much time explaining this never-really-working functionality.
Nonce Sum has been obsoleted / made historic (rfc8311)
You may want to update / enhance this talk with the Accurate ECN mechanism and the ACE field, as well as the AccECN handshake/negotation mechanism
Errate: ECE/CWR only has that semantic as explained while the SYN bit is set; the semantic changes during the actual data exchange.
Also CWR is bit 8 and NS used to be bit 9 (wrong order). But that is now the AE flag.
And the explanation of the CWR is completely incorrect as is the ECN mechanism. I hope everyone actually reads RFC3168 and doesn't take this as proper explanation.
In short:
Sender set's IP ECN to ECT(0) [on new data, not control, ACK, or retransmissions].
Congested Switch converts IP ECT(0) -> IP CE
Receiver latches ECE flag on the returned ACKs (reliable feedback of the IP CE codepoint, but only one CE per RTT possible)
Sender observes ECE, reduces congestion window as per the congestion algorithm and sends - on the next new data packet - CWR once.
Receiver clears the latched ECE once the CWR arrives - for about a decade most stacks had a bug, where a CE-marked CWR packet would *not* latch ECE on immediately again, btw.
It would be nice to redo this video (and remove the old version).
Crystal clear explanation... thanks a lot for this video... looking to understand TCP first and then later Wireshark. This video is a great start
Great sir thank you so much for making this video.
Thanks for the insightful explanation
*Thank You so much, Vaiyaa.*
Very informative video and explaination is very good.....
Thankyou for the informative video...
Thankyou for your comment. Please keep sharing buddy
At last found it, what i have been searching for a very long time 👍
Glad I could help
no he just tell the opposite
Excelent video!!!
What a simple yet amazing explanation! Subscribed ✅
Welcome aboard!
Your explanation was very nice, we are getting much clarification on tcp flags with your explanation. good job
Thankyou for your comment. Please keep sharing
Unfortunately, for the ECE, CWR, and NS part, it was also mostly entirely wrong. Spending time on URG was pointless as noone really uses/implements this any more.
Another excellent video👍 thanks for sharing such knowledge.
Glad you enjoyed it
Unfortunately, mostly wrong though
Very informative content
Glad you liked it
Really awesome bro
Thanks for commenting. Keep supporting
Such a great explanation. Thank you!
Thankyou for watching. Please keep supporting
Wonderfully explained. Thanks a lot bro
Thankyou for your comment. Please keep sharing
Awesome 👍
Thanks for the visit Glad to help
Great video
Thanks for the visit Glad to help
Fabulous work, Keep up the good work!
Thankyou for your comment. Please keep sharing
The Push flag explanation isn't correct. The Push flag itself means that push the data immediately to the application layer without being waiting for the entire segment to get filled. The Push flag indicates that you don't to wait anymore this is what is the end and you should send the segment ASAP to the upper layer.
The Urgent flag prioritize the data over other data. If there are multiple segments in the buffer and one of the segment has the pointer set then it will be processed first over the other segments.
Now if you have one segment with URG pointer set and other with Push, then obviously the URG will be prioritized first. Thanks!
once you push data on a connection you have to wait for the receiver to get all of it before it gets to the new data. This is where the URG flag kicks in. When you send urgent data, your TCP creates a special segment in which it sets the URG flag and also the urgent pointer field. This is what I got from the internet. I think he correct in video
Correctly said. Thanks for bringing in notice
#AaruneticTales
Right, Push definition is wrong in the video.
Great
Glad to help
In every networking site, clearly mentioned, that Push flag packet doesn't wait in the queue but urgent does.
Jeremy Stretch has a good write-up about it please read about it on internet. So now the telnet is connecting to a remote computer, we want to be able to have the commands we type executed right after we typed them. That is why they are flagged with URG flag.
Thankyou for your comment. I hope this clear to you.
🎉 Great job is there a way for us to send you a donation.
Your comment and support is highly great for us. Please keep supporting and sharing.
sir what is the difference between TCP and UDP
ua-cam.com/video/HBLSf7zwj6g/v-deo.html, watch here or go to the playlist
What is XMAS flag ?
Thankyou for Asking and sorry for replying late. So Xmas flag is nothing but a term being used to identify a kind of attack. In which attacker turn on three important flags( SYN, URG & PUSH) which make the destination device busy or over load it to stop processing the legitimate traffic. You can find this if you have any wireshark capture for DDOS attack.
sir the difference between push and urgent flags as u mentioned is totally wrong ...u need to check it again because u just tell the opposite ...sir telnet uses push not urgent sir please think about it
Thankyou for you query-:) Because telnet is connecting to a remote computer, we want to be able to have the commands we type executed right after we typed them. That is why they are flagged with URG flag. I hope this clear you.
@@TechClouts telnet and ssh use push flags ..not urgent...i have checked wireshark too... because push bypasses tcp buffer on both ends.
Clout
its ok but not in details , need to improve
Thankyou for your comment. We will work on it soon 🙂