Exit Zen
36
../../bibliography.rst:114
English
Eng Keong Lua, Crowcroft, J., Pias, M., Sharma, R., Lim, S., `A survey and comparison of peer-to-peer overlay network schemes <https://dx.doi.org/10.1109/COMST.2005.1610546>`_, Communications Surveys & Tutorials, IEEE, Volume: 7 , Issue: 2, 2005, pp. 72-93
0/2560 · 256
36
../../glossary.rst:150
English
EGP
0/100 · 3
36
../../exercises/ex-sharing.rst:639
English
In a deployed CSMA/CD network, would it be possible to increase or decrease the duration of the slotTime ? Justify your answer
0/1260 · 126
36
../../principles/transport.rst:74
English
The :term:`ASCII` characters are encoded as a seven bits field, but transmitted as an eight-bits byte whose high order bit is usually set to `0`. Bytes are always transmitted starting from the high order or most significant bit.
0/2280 · 228
36
../../principles/sharing.rst:163
English
Let us first explore which mechanisms can be used inside a network to control congestion and how these mechanisms can influence the behavior of the end hosts.
0/1580 · 158
36
../../exercises/ipv6.rst:350
English
on router ``R2``
0/160 · 16
36
../../exercises/routing-protocols.rst:436
English
``AS1`` is assigned ``2001:cafe:1::/48``
0/400 · 40
36
../../exercises/tcp-2.rst:326
English
A TCP stack uses both the fast retransmit technique and retransmission timers. A retransmission timer can fire after a fast retransmit when several segments are lost. The example below shows a loss of two consecutive segments. This script is available from :download:`/exercises/packetdrill_scripts/frr-rto.pkt`.
0/3120 · 312
36
../../protocols/bgp.rst:122
English
The BGP protocol :rfc:`4271` defines several types of messages that can be exchanged over a BGP session :
0/1050 · 105
36
../../protocols/congestion.rst:197
English
Evolution of the congestion window with regular losses
0/540 · 54
36
../../protocols/email.rst:181
English
`Content-Type: multipart/alternative`. This header line indicates that the MIME message contains several representations of the same information. For example, a `multipart/alternative` message may contain both a plain text and an HTML version of the same text.
0/2600 · 260
36
../../protocols/ethernet.rst:175
English
100Base-Tx
0/100 · 10
36
../../protocols/http.rst:153
English
the `POST` method can be used by a client to send a document to a server. The document is attached to the HTTP request as a MIME document.
0/1380 · 138
36
../../protocols/ipv6.rst:126
English
``2001:0db8:0000:cd30:0000:0000:0000:0000`` / ``60``
0/520 · 52
36
../../protocols/ethernet.rst:118
English
The introduction of the twisted pairs led to two major changes to Ethernet. The first change concerns the physical topology of the network. 10Base2 and 10Base5 networks are shared buses, the coaxial cable typically passes through each room that contains a connected computer. A 10BaseT network is a star-shaped network. All the devices connected to the network are attached to a twisted pair cable that ends in the telecom closet. From a maintenance perspective, this is a major improvement. The cable is a weak point in 10Base2 and 10Base5 networks. Any physical damage on the cable broke the entire network and when such a failure occurred, the network administrator had to manually check the entire cable to detect where it was damaged. With 10BaseT, when one twisted pair is damaged, only the device connected to this twisted pair is affected and this does not affect the other devices. The second major change introduced by 10BaseT was that is was impossible to build a 10BaseT network by simply connecting all the twisted pairs together. All the twisted pairs must be connected to a relay that operates in the physical layer. This relay is called an `Ethernet hub`. A `hub` is thus a physical layer relay that receives an electrical signal on one of its interfaces, regenerates the signal and transmits it over all its other interfaces. Some `hubs` are also able to convert the electrical signal from one physical layer to another (e.g. 10BaseT to 10Base2 conversion).
0/14740 · 1474
36
../../protocols/routing.rst:106
English
The first summary advertisement provides precise information about the distance used to reach each prefix. However, all routers in the network have to maintain a route towards `2001:db8:aaaa:0000::/64` and a route towards `2001:db8:aaaa:0001::/64` that are both via router `RA`. The second advertisement would improve the scalability of OSPF by reducing the number of routes that are advertised across area boundaries. However, in practice this requires manual configuration on the border routers.
0/4970 · 497
36
../../protocols/rpc.rst:122
English
`data`: an optional field that provides additional information about the error.
0/790 · 79
36
../../protocols/ssh.rst:269
English
Among the various features of the ``ssh`` protocol, it is interesting to mention how users are authenticated by the server. The ``ssh`` protocol supports the classical username/password authentication (but both the username and the password are transmitted over the secure encrypted channel). In addition, ``ssh`` supports two authentication mechanisms that rely on public keys. To use the first one, each user needs to generate his/her own public/private key pair and store the public key on the server. To be authenticated, the user needs to sign a message containing his/her public key by using his/her private key. The server can easily verify the validity of the signature since it already knows the user's public key. The second authentication scheme is designed for hosts that trust each other. Each host has a public/private key pair and stores the public keys of the other hosts that it trusts. This is typically used in environments such as university labs where each user could access any of the available computers. If Alice has logged on ``computer1`` and wants to execute a command on ``computer2``, she can create an ``ssh`` session on this computer and type (again) her password. With the host-based authentication scheme, ``computer1`` signs a message with its private key to confirm that it has already authenticated Alice. ``computer2`` would then accept Alice's session without asking her credentials.
0/14210 · 1421
36
../../protocols/tcp.rst:116
English
Upon reception of this segment (which is often called a `SYN segment`), the server host replies with a segment containing :
0/1230 · 123
36
../../protocols/tls.rst:150
English
`Random number`: security protocols rely on random numbers. The client sends a 32 bytes long random number where usually four of these bytes correspond to the client's clock. This random number is used, together with the server's random number, as a seed to generate the security keys.
0/2850 · 285