Exit Zen
54
../../exercises/tcp-2.rst:686
English
Can you explain why the congestion window is increased after the reception of the first acknowledgment ?
0/1040 · 104
55
../../exercises/tcp-2.rst:688
English
How long does it take for the sender to deliver 3 KBytes to the receiver ?
0/740 · 74
56
../../exercises/tcp-2.rst:691
English
Same question as above but now with a small variation. Recent TCP implementations use a large initial value for the congestion window. Draw the time-sequence diagram that corresponds to an initial value of 10000 bytes for this congestion window.
0/2450 · 245
57
../../exercises/tcp-2.rst:715
English
Same question as the first one, but consider that the MSS on the sender is set to 500 bytes. How does this modification affect the entire delay ?
0/1450 · 145
58
../../exercises/tcp-2.rst:738
English
Assuming that there are no losses and that there is no congestion in the network. If the sender writes `x` bytes on a newly established TCP connection, derive a formula that computes the minimum time required to deliver all these `x` bytes to the receiver. For the derivation of this formula, assume that `x` is a multiple of the maximum segment size and that the receive window and the slow-start threshold are larger than `x`.
0/4280 · 428
59
../../exercises/tcp-2.rst:740
English
In question 1, we assumed that the receiver acknowledged every segment received from the sender. In practice, many deployed TCP implementations use delayed acknowledgments. Assuming a delayed acknowledgment timer of 50 milliseconds, modify the time-sequence diagram below to reflect the impact of these delayed acknowledgment. Does their usage decreases or increased the transmission delay ?
0/3910 · 391
60
../../exercises/tcp-2.rst:775
English
Let us now explore the impact of congestion on the slow-start and congestion avoidance mechanisms. Consider the scenario below. For graphical reasons, it is not possible anymore to show information about the segments on the graph, but you can easily infer them.
0/2610 · 261
61
../../exercises/tcp-2.rst:832
English
Redraw the same figure assuming that the second segment that was delivered by the sender in the figure experienced congestion. In a network that uses Explicit Congestion Notification, this segment would be marked by routers and the receiver would return the congestion mark in the corresponding acknowledgment.
0/3100 · 310
62
../../exercises/tcp-2.rst:834
English
Same question, but assume now that the fourth segment delivered by the sender experienced congestion (but was not discarded).
0/1250 · 125
63
../../exercises/tcp-2.rst:837
English
A TCP connection has been active for some time and has reached a congestion window of 4000 bytes. Four segments are sent, but the second (shown in red in the figure) is corrupted. Complete the time-sequence diagram.
0/2150 · 215
65
../../exercises/tcp-2.rst:876
English
On Linux, most of the parameters to tune the TCP stack are accessible via :manpage:`sysctl`. These parameters are briefly described in https://github.com/torvalds/linux/blob/master/Documentation/networking/ip-sysctl.txt and in the :manpage:`tcp` manpage. Each script sets some of these configuration variables.
0/3100 · 310
66
../../exercises/tcp-2.rst:883
English
packetdrill_ requires root privileges since it inject raw IP packets. The easiest way to install it is to use a virtualbox image with a Linux kernel 4.x or 5.x. You can clone its git repository from https://github.com/google/packetdrill and follow the instructions in https://github.com/google/packetdrill/tree/master/gtests/net/packetdrill. The packetdrill_ scripts used in this section are available from https://github.com/cnp3/ebook/tree/master/exercises/packetdrill_scripts
0/4780 · 478
67
../../exercises/tcp-2.rst:885
English
By default, packetdrill_ uses port 8080 when creating TCP segments. You can thus capture the packets injected by packetdrill_ and the responses from the stack by using ``tcpdump -i any -n port 8080``
0/1990 · 199
68
../../exercises/tcp-2.rst:887
English
The `Push` flag is one of the TCP flags defined in :rfc:`793`. TCP stacks usually set this flag when transmitting a segment that empties the send buffer. This is the reason why we observe this push flag in our example.
0/2180 · 218
69
../../exercises/tcp-2.rst:889
English
The variables that are included in TCP_INFO are defined in https://github.com/torvalds/linux/blob/master/include/uapi/linux/tcp.h
0/1290 · 129
70
../../exercises/tcp-2.rst:891
English
These states are defined in https://github.com/torvalds/linux/blob/master/include/net/tcp_states.h
0/980 · 98
The translation has come to an end.