Exit Zen
30
../../exercises/ipv6.rst:294
English
``p:12/64`` for the link between ``R1`` and ``R2``. On this subnet, ``R1`` uses address ``p:12::1`` while router ``R2`` uses address ``p:12::2``
0/1440 · 144
30
../../exercises/routing-protocols.rst:366
English
Router ``r2`` receives a similar request from ``fe80::481a:48ff:fed7:292e`` and replies by sending its routing table in a response message. Note that this message is sent to the link-local address of the requesting router.
0/2220 · 222
30
../../exercises/tcp-2.rst:191
English
Another usage of packetdrill_ is to explore how a TCP connection ends. The scripts below show how a TCP stack closes a TCP connection. The first example shows a local host that connects to a remote host and then closes the connection. The remote host acknowledges the ``FIN`` and later closes its direction of data transfer. This script is available from :download:`/exercises/packetdrill_scripts/local-close.pkt`.
0/4140 · 414
30
../../protocols/bgp.rst:99
English
The Internet uses a single interdomain routing protocol : the Border Gateway Protocol (BGP). The current version of BGP is defined in :rfc:`4271`. BGP differs from the intradomain routing protocols that we have already discussed in several ways. First, BGP is a `path-vector` protocol. When a BGP router advertises a route towards a prefix, it announces the IP prefix and the interdomain path used to reach this prefix. From BGP's point of view, each domain is identified by a unique `Autonomous System` (AS) number [#fasdomain]_ and the interdomain path contains the AS numbers of the transit domains that are used to reach the associated prefix. This interdomain path is called the `AS Path`. Thanks to these AS-Paths, BGP does not suffer from the count-to-infinity problems that affect distance vector routing protocols. Furthermore, the AS-Path can be used to implement some routing policies. Another difference between BGP and the intradomain routing protocols is that a BGP router does not send the entire contents of its routing table to its neighbors regularly. Given the size of the global Internet, routers would be overloaded by the number of BGP messages that they would need to process. BGP uses incremental updates, i.e. it only announces the routes that have changed to its neighbors.
0/12990 · 1299
30
../../protocols/congestion.rst:178
English
routers that have several queues served by a round-robin scheduler
0/660 · 66
30
../../protocols/dnssec.rst:332
English
See http://spoofer.caida.org/summary.php for an ongoing measurement study that analyses the networks where an attacker could send packets with any source IP address.
0/1650 · 165
30
../../protocols/email.rst:172
English
:rfc:`2045` defines three new types of header lines to support MIME :
0/690 · 69
30
../../protocols/ethernet.rst:172
English
10Base2
0/100 · 7
30
../../protocols/http.rst:122
English
a `status line` , that indicates whether the request was successful or not
0/740 · 74
30
../../protocols/http2.rst:226
English
The first frame that a client sends over an HTTP/2.0 session is the `Settings` frame. This is a control frame that indicates some parameters that the client proposes for this session. Several of these parameters are defined in :rfc:`7540`. The most important ones are probably the `SETTINGS_MAX_FRAME_SIZE` that specifies the maximum length of the HTTP/2.0 frames that this implementation supports and the `SETTINGS_MAX_CONCURRENT_STREAMS` that specifies the maximum number of parallel streams that this implementation can manage. The `SETTINGS_MAX_FRAME_SIZE` must be at least :math:`2^{14}` bytes but can go up to :math:`2^{24} -1` bytes. There is no minimum value for `SETTINGS_MAX_CONCURRENT_STREAMS`, but :rfc:`7540` recommends to support at least 100 different stream identifiers.
0/7860 · 786
30
../../protocols/ipv6.rst:117
English
IPv6 addresses often contain a long sequence of bits set to ``0``. In this case, a compact notation has been defined. With this notation, `::` is used to indicate one or more groups of 16 bits blocks containing only bits set to `0`. For example,
0/2450 · 245
30
../../protocols/ethernet.rst:94
English
An Ethernet network provides an unreliable connectionless service. It supports three different transmission modes : `unicast`, `multicast` and `broadcast`. While the Ethernet service is unreliable in theory, a good Ethernet network should, in practice, provide a service that:
0/2760 · 276
30
../../protocols/routing.rst:96
English
`RB` advertises `2001:db8:1234::/48` at a distance of `2` and `2001:db8:5678::/48` at a distance of `3`
0/1030 · 103
30
../../protocols/rpc.rst:115
English
`jsonrpc`: a string indicating the version of the protocol used to encode the response
0/860 · 86
30
../../protocols/ssh.rst:227
English
``payload`` : the data (after optional compression) passed by the user
0/700 · 70
30
../../protocols/tcp.rst:58
English
the `Optional header extension` is used to add optional information to the TCP header. Thanks to this header extension, it is possible to add new fields to the TCP header that were not planned in the original specification. This allowed TCP to evolve since the early eighties. The details of the TCP header extension are explained in sections :ref:`TCPOpen` and :ref:`TCPReliable`.
0/3810 · 381
30
../../protocols/tls.rst:100
English
Verify that the client interacts with a valid server
0/520 · 52
30
../../protocols/wifi.rst:26
English
150 Mbps
0/100 · 8
31
../../bibliography.rst:99
English
Kerrisk, M., `The Linux Programming Interface <http://nostarch.com/tlpi>`_, No Starch Press, 2010
0/970 · 97
31
../../exercises/ex-sharing.rst:609
English
In this network, a 250 Kbps link is used between the routers. The propagation delays in the network are negligible. Host `A` sends 1000 bits long segments so that it takes one msec to transmit one segment on the `A-R1` link. Neglecting the transmission delays for the acknowledgments, what is the minimum round-trip time measured on host `A` with such segments ?
0/3620 · 362