Exit Zen
20
../../glossary.rst:156
English
BGP
0/100 · 3
20
../../exercises/ex-sharing.rst:432
English
In practice, a router is connected to multiple input links. The figure below shows an example with two hosts.
0/1090 · 109
20
../../exercises/reliability.rst:42
English
when every second acknowledgment is discarded due to transmission errors
80/720 · 72
20
../../exercises/network.rst:178
English
`R3->R2->R4->R5` and `R1->R2->R5`
32/330 · 33
20
../../exercises/sockets.rst:175
English
Using this code, the program will read and print an arbitrary message received from an arbitrary peer who knows the program's socket address. If we want to know the address of the peer that sent us the message, we can use the ``recvfrom`` system call. This is what a modified version of ``bind_and_receive_from_peer`` is doing below.
369/3330 · 333
20
../../exercises/transport.rst:142
English
DATA segments contain a sequence number that is incremented for each DATA segment transmitted
108/930 · 93
20
../../principles/naming.rst:112
English
To retrieve the mapping for host `h2.dom`, a client sends its query to the name server that is responsible for domain `.dom`. The name server directly answers the query. To retrieve a mapping for `h3.a.sdom1.dom` a DNS client first sends a query to the name server that is responsible for the `.dom` domain. This nameserver returns the nameserver that is responsible for the `sdom1.dom` domain. This nameserver can now be contacted to obtain the nameserver that is responsible for the `a.sdom1.dom` domain. This nameserver can be contacted to retrieve the mapping for the `h3.a.sdom1.dom` name. Thanks to this structure, it is possible for a DNS client to obtain the mapping of any host inside the `.dom` domain or any of its subdomains. To ensure that any DNS client will be able to resolve any fully qualified domain name, there are special nameservers that are responsible for the root of the domain name hierarchy. These nameservers are called :term:`root nameserver`.
1014/9720 · 972
20
../../principles/network.rst:87
English
the network layer address of the destination host
55/490 · 49
20
../../principles/reliability.rst:54
English
:math:`10^{12}`
15/150 · 15
20
../../principles/transport.rst:50
English
Alice : `3.1415`
16/160 · 16
20
../../principles/sharing.rst:103
English
In the above network, the allocation of all flows would grow until `A1-A2` and `B1-B2` reach 5 Mbps. At this point, link `R1-R2` becomes congested and these two flows have reached their maximum. The allocation for flow `C1-C2` can increase until reaching 15 Mbps. At this point, link `R2-R3` is congested. To increase the bandwidth allocated to `C1-C2`, one would need to reduce the allocation to flow `B1-B2`. Similarly, the only way to increase the allocation to flow `B1-B2` would require a decrease of the allocation to `A1-A2`.
0/5320 · 532
20
../../protocols/dns.rst:67
English
Reverse DNS
11/110 · 11
20
../../principles/security.rst:270
English
`A cryptographic algorithm should be secure even if the attacker knows everything about the system, except one parameter known as the secret key.`
0/1460 · 146
20
../../exercises/dns.rst:55
English
What is the lifetime associated to this IPv6 address ?
0/540 · 54
20
../../exercises/ipv6.rst:151 • ../../exercises/ipv6.rst:229
English
router ``R3`` uses address ``2001:db8:1341:34::3`` on its East interface and address ``2001:db8:1341:13::3`` on its North interface
0/1310 · 131
20
../../exercises/lan.rst:195
English
The network contains five nodes and six links.
0/460 · 46
20
../../exercises/routing-policies.rst:167
English
A ``traceroute6`` towards ``ipv6.google.com`` provides the following output :
0/770 · 77
20
../../exercises/routing-protocols.rst:261
English
The requested information is sent in a `LS Update` packet shortly after that.
0/770 · 77
20
../../exercises/tcp-2.rst:113
English
packetdrill_ writes 10 bytes of data through the :manpage:`write` system call. The stack immediately sends these 10 bytes inside a segment whose ``Push`` flag is set [#fpush]_. The payload starts at sequence number ``1`` and ends at sequence number ``10``. packetdrill_ replies by injecting an acknowledgment for the entire data after 100 milliseconds.
0/3520 · 352
20
../../exercises/trace.rst:109
English
When analyzing packet traces with wireshark_, it is often very useful to use `Display filters` that only show the packets that match some specific criteria. There filters are described in several online documents:
0/2130 · 213