Exit Zen
17
../../exercises/ipv6.rst:94
English
Consider the same network as in the previous question, but now the forwarding tables of ``R2`` and ``R3`` are configured as shown below :
0/1370 · 137
17
../../exercises/lan.rst:117
English
IPMininet_ can also be used to configure the Spanning Tree protocol on Linux hosts that act as Ethernet switches. Let us consider the simple Ethernet network shown in the figure below.
0/1840 · 184
17
../../exercises/routing-policies.rst:157
English
Consider the network shown below. In this network, the metric of each link is set to `1` except link `A-B` whose metric is set to `4` in both directions. In this network, there are two paths with the same cost between `D` and `C`. Old routers would randomly select one of these equal cost paths and install it in their forwarding table. Recent routers are able to use up to `N` equal cost paths towards the same destination.
0/4240 · 424
17
../../exercises/routing-protocols.rst:249
English
We can then observe the Database description packet that is sent by routers to announce the state of their OSPFv3 database. The details of this packet are beyond the scope of this simple exercise.
0/1960 · 196
17
../../exercises/tcp-2.rst:95
English
This TCP segment is sent immediately by the stack. The ``SYN`` flag is set and the dot next to the ``S`` character indicates that the ACK flag is also set. The SYN+ACK segment does not contain any data but its acknowledgment number is set to 1 (relative to the initial sequence number). For outgoing packets, packetdrill_ does not verify the value of the advertised window. In this line, it also accepts any TCP options (``<...>``).
0/4320 · 432
17
../../exercises/trace.rst:98
English
The second tool is the flow graph that is part of the `Statistics` menu. It provides a time sequence diagram of the packets exchanged with some comments about the packet contents. See below for an example.
0/2050 · 205
17
../../protocols/bgp.rst:60
English
The second rule ensures that the customer domain receives a route towards all destinations that are reachable via its provider. The first rule allows the prefixes of the customer domain to be distributed throughout the Internet.
0/2280 · 228
17
../../protocols/congestion.rst:98
English
Controlling congestion without losing data
0/420 · 42
17
../../protocols/dnssec.rst:173
English
the `NSEC` record is used when non-existent domain names are queried. Its usage will be explained later
0/1030 · 103
17
../../protocols/email.rst:103
English
Other header lines appear in most email messages. The `Subject:` header line allows the sender to indicate the topic discussed in the email. Three types of header lines can be used to specify the recipients of a message :
0/2210 · 221
17
../../protocols/ethernet.rst:97
English
does not reorder the transmitted frames
0/390 · 39
17
../../protocols/http.rst:80
English
The third part of the URI is the path to the document. This path is structured as filenames on a Unix host (but it does not imply that the files are indeed stored this way on the server). If the path is not specified, the server will return a default document. The last two optional parts of the URI are used to provide a query parameter and indicate a specific part (e.g. a section in an article) of the requested document. Sample URIs are shown below.
0/4530 · 453
17
../../protocols/http2.rst:109
English
With `pipelining`, the client sends the five requests immediately and receives the five responses after 200 msec. The figure below illustrates the benefits of `pipelining`.
0/1720 · 172
17
../../protocols/ipv6.rst:95
English
IPv6 addresses are encoded as a 128 bits field
0/460 · 46
17
../../protocols/ethernet.rst:12
English
Ethernet was designed in the 1970s at the Palo Alto Research Center [Metcalfe1976]_. The first prototype [#fethernethistory]_ used a coaxial cable as the shared medium and 3 Mbps of bandwidth. Ethernet was improved during the late 1970s and in the 1980s, Digital Equipment, Intel and Xerox published the first official Ethernet specification [DIX]_. This specification defines several important parameters for Ethernet networks. The first decision was to standardize the commercial Ethernet at 10 Mbps. The second decision was the duration of the `slot time`. In Ethernet, a long `slot time` enables networks to span a long distance but forces the host to use a larger minimum frame size. The compromise was a `slot time` of 51.2 microseconds, which corresponds to a minimum frame size of 64 bytes.
0/7980 · 798
17
../../protocols/routing.rst:58
English
A note on timers
0/160 · 16
17
../../protocols/rpc.rst:58
English
In some situations, it is necessary to encode fixed or variable length arrays. XDR :rfc:`1832` supports such arrays. For example, the encoding below corresponds to a variable length array containing n elements. The encoded representation starts with an integer that contains the number of elements and follows with all elements in sequence. It is also possible to encode a fixed-length array. In this case, the first integer (the `n` field) is missing.
0/4520 · 452
17
../../protocols/ssh.rst:140
English
the server generates the random number :math:`b`. It then computes :math:`B=g^{b} \mod p`, :math:`K=B^{a} \mod p` and signs with its private key :math:`hash(V_{Client} || V_{Server} || KEX\_INIT_{Client} || KEX\_INIT_{Server} || Server_{pub} || A || B || K )` where :math:`V_{Server}` (resp. :math:`V_{Client}`) is the initial messages sent by the client (resp. server), :math:`KEX\_INIT_{Client}` (resp. :math:`KEX\_INIT_{Server}`) is the key exchange message sent by the client (resp. server) and :math:`A`, :math:`B` and :math:`K` are the messages of the Diffie Hellman key exchange
0/5860 · 586
17
../../protocols/tcp.rst:42
English
the port chosen by the server
0/290 · 29
17
../../protocols/tls.rst:45
English
563
0/100 · 3