Exit Zen
32
../../exercises/routing-protocols.rst:374
English
The packet traces collected on the three routers of this example are available from :download:`/exercises/traces/ripng-r1-trace.pcap`, :download:`/exercises/traces/ripng-r2-trace.pcap` and :download:`/exercises/traces/ripng-r3-trace.pcap`.
0/2390 · 239
32
../../exercises/tcp-2.rst:234
English
A third scenario for the termination of a TCP connection is that the remote hosts sends its ``FIN`` first. This script is available from :download:`/exercises/packetdrill_scripts/remote-close.pkt`.
0/1970 · 197
32
../../protocols/bgp.rst:106
English
Simple exchange of BGP routes
0/290 · 29
32
../../protocols/congestion.rst:182
English
If the router uses several queues served by a scheduler, the situation is different. If a large and a small flow are competing for bandwidth, the scheduler will already favor the small flow that is not using its fair share of the bandwidth. The queue for the small flow will be almost empty while the queue for the large flow will build up. On routers using such schedulers, a good way of marking the packets is to set a threshold on the occupancy of each queue and mark the packets that arrive in a particular queue as soon as its occupancy is above the configured threshold.
0/5760 · 576
32
../../protocols/email.rst:175
English
The `Content-Type:` header line indicates the type of data that is carried inside the message (see below).
0/1060 · 106
32
../../protocols/ethernet.rst:173
English
10BaseT
0/100 · 7
32
../../protocols/http.rst:124
English
a MIME document
0/150 · 15
32
../../protocols/http2.rst:230
English
Another feature of HTTP/2.0 is that it is possible to assign different priorities to different streams. A high priority stream should carry more `Data` frames than a lower priority ones. The HTTP/2.0 specification defines `Priority` frames which can be used for this purpose.
0/2750 · 275
32
../../protocols/ipv6.rst:120
English
``ff01:0:0:0:0:0:0:101`` is represented as ``ff01::101``
0/580 · 58
32
../../protocols/ethernet.rst:97
English
does not reorder the transmitted frames
0/390 · 39
32
../../protocols/routing.rst:99
English
These summary advertisements are flooded through the backbone area attached to routers `RB` and `RC`. In its routing table, router `RA` selects the summary advertised by `RB` to reach `2001:db8:1234::/48` and the summary advertised by `RC` to reach `2001:db8:5678::/48`. Inside `area 1`, router `RA` advertises a summary indicating that `2001:db8:1234::/48` and `2001:db8:5678::/48` are both at a distance of `3` from itself.
0/4250 · 425
32
../../protocols/rpc.rst:117
English
`result`: if the request succeeded, this member contains the result of the request (in our example, value `4`).
0/1110 · 111
32
../../protocols/ssh.rst:231
English
``MAC`` : this field is present if a Message Authentication Code has been negotiated for the session (in practice, using ``ssh`` without authentication is risky and this field should always be present). Note that to compute the MAC, an ``ssh`` implementation must maintain a message counter. This counter is incremented by one every time a message is sent and the MAC is computed with the negotiated authentication algorithm using the MAC key over the concatenation of the message counter and the cleartext message. The message counter is not transmitted, but the recipient can easily recover its value. The ``MAC`` is computed as :math:`mac = MAC(key, sequence\_number || unencrypted\_message)` where the key is the negotiated authentication key.
0/7470 · 747
32
../../protocols/tcp.rst:107
English
TCP connection establishment
0/280 · 28
32
../../protocols/tls.rst:105
English
The TLS handshake is a four-way handshake illustrated in the figure below.
0/740 · 74
32
../../protocols/wifi.rst:29
English
When developing its family of standards, the `IEEE 802.11 working group <http://www.ieee802.org/11/>`_ took a similar approach as the `IEEE 802.3 working group <http://www.ieee802.org/3/>`_ that developed various types of physical layers for Ethernet networks. 802.11 networks use the CSMA/CA Medium Access Control technique described earlier and they all assume the same architecture and use the same frame format.
0/4150 · 415
33
../../bibliography.rst:106
English
Kung, N.T. Morris, R., `Credit-based flow control for ATM networks <https://dx.doi.org/10.1109/65.372658>`_, IEEE Network, Mar/Apr 1995, Volume: 9, Issue: 2, pages: 40-48
0/1730 · 173
33
../../exercises/ex-sharing.rst:611
English
Same question as above, but now host `A` uses the simple DECBIT congestion control mechanism and a maximum window size of four segments.
0/1360 · 136
33
../../exercises/network.rst:325
English
Host `A` uses the same flat address for both links.
61/510 · 51
33
../../exercises/sockets.rst:284
English
The ``2001:6a8:308f:9:0:82ff:fe68:e520`` IPv6 address identifies the computer serving the ``https://beta.computer-networking.info`` website.
137/1400 · 140