Exit Zen
42
../../bibliography.rst:132
English
Metcalfe R., Boggs, D., `Ethernet: Distributed packet-switching for local computer networks <http://doi.acm.org/10.1145/360248.3602530>`_. Communications of the ACM, 19(7):395--404, 1976.
0/1870 · 187
42
../../glossary.rst:319
English
file transfer
0/130 · 13
42
../../exercises/reliability.rst:91
English
Same question as above, but assume now that both the sender and the receiver implement selective repeat. Note that the answer can be different from the above question.
0/1670 · 167
42
../../principles/network.rst:147
English
The first technique assumes that the underlying network topology is a tree. A tree is the simplest network to be considered when forwarding packets. The main advantage of using a tree is that there is only one path between any pair of nodes inside the network. Since a tree does not contain any cycle, it is impossible to have forwarding loops in a tree-shaped network.
0/3690 · 369
42
../../principles/sharing.rst:182
English
`Which packet(s) should be discarded ?` Once the network node has decided to discard packets, it needs to actually discard real packets.
0/1360 · 136
42
../../principles/security.rst:412
English
In practice, encrypting a message to sign it can be computationally costly, in particular if the message is a large file. A faster solution would be to summarize the document and only sign the summary of the document. A naive approach could be based on a checksum or CRC computed over the message. Alice would then compute :math:`C=Checksum(M)` and :math:`SC=E_p(A_{priv},C)`. She would then send both `M` and `SC` to the recipient of the message who can easily compute `C` from `SC` and verify the authenticity of the message. Unfortunately, this solution does not protect Alice and the message's recipient against a man-in-the-middle attack. If Mallory can intercept the message sent by Alice, he can easily modify Alice's message and tweak it so that it has the same checksum as the original one. The CRCs, although more complex to compute, suffer from the same problem.
0/8730 · 873
42
../../exercises/ipv6.rst:436
English
Sometimes, static routes must be configured on networks to enforce certain paths. Consider the six routers network shown in the figure below.
0/1410 · 141
42
../../exercises/routing-protocols.rst:512
English
We can now run this simple network.
0/350 · 35
42
../../exercises/tcp-2.rst:593
English
Our last scenario is when the first segment sent is lost. In this case, two round-trip-times are required to retransmit the missing segment and recover from the loss. This script is available from :download:`/exercises/packetdrill_scripts/slow-start-frr3.pkt`.
0/2600 · 260
42
../../protocols/bgp.rst:131
English
a list of IP prefixes that are withdrawn
0/400 · 40
42
../../protocols/congestion.rst:211
English
TCP connections with a small round-trip-time can achieve a higher throughput than TCP connections having a longer round-trip-time when losses occur. This implies that the TCP congestion control scheme is not completely fair since it favors the connections that have the shorter round-trip-times.
0/2950 · 295
42
../../protocols/email.rst:214
English
`audio`. The message part contains an audio clip. The subtype indicates the format of the audio clip like `wav <http://en.wikipedia.org/wiki/Wav>`_ or `mp3 <http://en.wikipedia.org/wiki/Mp3>`_.
0/1930 · 193
42
../../protocols/ethernet.rst:178
English
1000Base-SX
0/110 · 11
42
../../protocols/http.rst:164
English
the `Server:` header indicates the version of the web server that has generated the HTTP response. Some servers provide information about their software release and optional modules that they use. For security reasons, some system administrators disable these headers to avoid revealing too much information about their server to potential attackers.
0/3500 · 350
42
../../protocols/ipv6.rst:156
English
A `subnet identifier` that identifies a customer of the ISP
0/590 · 59
42
../../protocols/ethernet.rst:169
English
Comments
0/100 · 8
42
../../protocols/routing.rst:139
English
How to quickly detect a link failure ?
0/380 · 38
42
../../protocols/tcp.rst:129
English
At this point, the TCP connection is open and both the client and the server are allowed to send TCP segments containing data. This is illustrated in the figure below.
0/1670 · 167
42
../../protocols/tls.rst:190
English
The server replies to the ``ClientHello`` with several messages:
0/640 · 64
42
../../protocols/wifi.rst:107
English
When a frame is sent from a WiFi device to a server attached to the same LAN as the access point, the first address of the frame is set to the MAC address of the access point, the second address is set to the MAC address of the source WiFi device and the third address is the address of the final destination on the LAN. When the server replies, it sends an Ethernet frame whose source address is its MAC address and the destination address is the MAC address of the WiFi device. This frame is captured by the access point that converts the Ethernet header into an 802.11 frame header. The 802.11 frame sent by the access point contains three addresses : the first address is the MAC address of the destination WiFi device, the second address is the MAC address of the access point and the third address the MAC address of the server that sent the frame.
0/8540 · 854