Exit Zen
20
../../protocols/wifi.rst:23
English
35/120
0/100 · 6
21
../../bibliography.rst:67
English
Francois, P., Filsfils, C., Evans, J., and Bonaventure, O., `Achieving sub-second IGP convergence in large IP networks <http://doi.acm.org/10.1145/1070873.1070877>`_. SIGCOMM Computer Communication Review 35, 3 (Jul. 2005), 35-44.
0/2300 · 230
21
../../glossary.rst:158
English
The Border Gateway Protocol is the interdomain routing protocol used in the global Internet.
0/920 · 92
21
../../exercises/ex-sharing.rst:491
English
In general, the links have a non-zero delay. This is illustrated in the figure below where a delay has been added on the link between `R` and `C`.
0/1460 · 146
21
../../exercises/reliability.rst:44
English
Same question when using selective repeat instead of go-back-n. Note that the answer is not necessarily the same.
130/1130 · 113
21
../../exercises/network.rst:180
English
Is it possible to achieve these paths and if so what are the required forwarding tables ?
97/890 · 89
21
../../exercises/sockets.rst:213
English
This function is now using the ``recvfrom`` system call that will also provide the address of the peer who sent the message. As addresses are generic and can have different sizes, ``recvfrom`` also tells us the size of the address that it has written.
276/2510 · 251
21
../../exercises/transport.rst:144
English
Some transport protocols use 32 bits sequence numbers while others use 64 bits sequence number. What are the advantages and drawbacks of each approach ?
208/1520 · 152
21
../../principles/naming.rst:114
English
Each root nameserver maintains the list [#froot]_ of all the nameservers that are responsible for each of the top-level domain names and their addresses [#frootv6]_. All root nameservers cooperate and provide the same answers. By querying any of the root nameservers, a DNS client can obtain the nameserver that is responsible for any top-level-domain name. From this nameserver, it is possible to resolve any domain name.
483/4220 · 422
21
../../principles/network.rst:88
English
its own network layer address
38/290 · 29
21
../../principles/reliability.rst:59
English
To understand some of the principles behind the physical transmission of information, let us consider the simple case of an electrical wire that is used to transmit bits. Assume that the two communicating hosts want to transmit one thousand bits per second. To transmit these bits, the two hosts can agree on the following rules :
348/3300 · 330
21
../../principles/transport.rst:51
English
Bob : `This is not the correct password.`
41/410 · 41
21
../../principles/sharing.rst:106 • ../../principles/sharing.rst:172
English
Network congestion
0/180 · 18
21
../../protocols/dns.rst:69
English
The DNS is mainly used to find the address that corresponds to a given name. However, it is sometimes useful to obtain the name that corresponds to an IP address. This done by using the `PTR` (`pointer`) `RR`. The `RData` part of a `PTR` `RR` contains the name while the `Name` part of the `RR` contains the IP address encoded in the `in-addr.arpa` domain. IPv4 addresses are encoded in the `in-addr.arpa` by reversing the four digits that compose the dotted decimal representation of the address. For example, consider IPv4 address `192.0.2.11`. The hostname associated to this address can be found by requesting the `PTR` `RR` that corresponds to `11.2.0.192.in-addr.arpa`. A similar solution is used to support IPv6 addresses :rfc:`3596`, but slightly more complex given the length of the IPv6 addresses. For example, consider IPv6 address `2001:1890:123a::1:1e`. To obtain the name that corresponds to this address, we need first to convert it in a reverse dotted decimal notation : `e.1.0.0.1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.a.3.2.1.0.9.8.1.1.0.0.2`. In this notation, each character between dots corresponds to one nibble, i.e. four bits. The low-order byte (`e`) appears first and the high order (`2`) last. To obtain the name that corresponds to this address, one needs to append the `ip6.arpa` domain name and query for `e.1.0.0.1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.a.3.2.1.0.9.8.1.1.0.0.2.ip6.arpa`. In practice, tools and libraries do the conversion automatically and the user does not need to worry about it.
1625/15140 · 1514
21
../../principles/security.rst:279
English
This principle is important because it remains the basic assumption of all cryptographers. Any system that relies on the secrecy of its algorithm to be considered secure is doomed to fail and be broken one day.
0/2100 · 210
21
../../exercises/dns.rst:57
English
Perform the same analysis for a popular website such as `www.google.com`. What is the lifetime associated to the corresponding IPv6 address ? If you perform the same request several times, do you always receive the same answer ? Can you explain why a lifetime is associated to the DNS replies ?
0/2940 · 294
21
../../exercises/ipv6.rst:154
English
Routers ``R2`` and ``R3`` are buggy in this network. Besides the routes for their local interfaces (not shown in the figure), they only have a default route which is shown in the figure below.
0/1920 · 192
21
../../exercises/lan.rst:211
English
By using :manpage:`brtcl(8)`, we can easily observe the state of the Spanning Tree protocol on the different switches. Let us start with ``s3``, i.e. the root of the Spanning Tree.
0/1800 · 180
21
../../exercises/routing-policies.rst:191
English
Can you explain why at the eighth, ninth and tenth hopes several IPv6 addresses are reported in the ``traceroute6`` output ?
0/1240 · 124
21
../../exercises/routing-protocols.rst:265
English
OSPFv3 also includes `LS Acknowledge` packets that acknowledge the correct reception of link state information.
0/1110 · 111