cnp3-ebook/exercises/routing-policies

Exit Zen

1 ../../exercises/routing-policies.rst:5
	English Inter-domain routing
	English Inter-domain routing Inter-domain routing 20/10000 · 20 Needs editing
2 ../../exercises/routing-policies.rst:9
	English Exercises
	English Exercises Exercises 9/10000 · 9 Needs editing
3 ../../exercises/routing-policies.rst:24
	English Consider the interdomain topology shown in the figure below.
	English Consider the interdomain topology shown in the figure below. Consider the interdomain topology shown in the figure below. 60/10000 · 60 Needs editing
4 ../../exercises/routing-policies.rst:56
	English In this network, what are the paths :
	English In this network, what are the paths : In this network, what are the paths : 37/10000 · 37 Needs editing
5 ../../exercises/routing-policies.rst:58
	English from `AS1` to `AS4`
	English from `AS1` to `AS4` from `AS1` to `AS4` 19/10000 · 19 Needs editing
6 ../../exercises/routing-policies.rst:59
	English from `AS4` to `AS2`
	English from `AS4` to `AS2` from `AS4` to `AS2` 19/10000 · 19 Needs editing
7 ../../exercises/routing-policies.rst:60
	English from `AS4` to `AS1`
	English from `AS4` to `AS1` from `AS4` to `AS1` 19/10000 · 19 Needs editing
8 ../../exercises/routing-policies.rst:63 • ../../exercises/routing-policies.rst:96
	English Consider the interdomain topology shown in the figure below. Assuming, that `AS1` advertises prefix ``2001:db8:1::/48``, `AS2` prefix ``2001:db8:2::/48``, ... compute the routing tables of the different ASes.
	English Consider the interdomain topology shown in the figure below. Assuming, that `AS1` advertises prefix ``2001:db8:1::/48``, `AS2` prefix ``2001:db8:2::/48``, ... compute the routing tables of the different ASes. Consider the interdomain topology shown in the figure below. Assuming, that `AS1` advertises prefix ``2001:db8:1::/48``, `AS2` prefix ``2001:db8:2::/48``, ... compute the routing tables of the different ASes. 209/10000 · 209 Needs editing
9 ../../exercises/routing-policies.rst:93
	English Are all ASes capable of reaching all the other ASes in this simple Internet ?
	English Are all ASes capable of reaching all the other ASes in this simple Internet ? Are all ASes capable of reaching all the other ASes in this simple Internet ? 77/10000 · 77 Needs editing
10 ../../exercises/routing-policies.rst:128
	English In this internet, some ASes cannot reach all other ASes. Can you fix the problem by adding one shared-cost peering link or one customer-provider peering link ?
	English In this internet, some ASes cannot reach all other ASes. Can you fix the problem by adding one shared-cost peering link or one customer-provider peering link ? In this internet, some ASes cannot reach all other ASes. Can you fix the problem by adding one shared-cost peering link or one customer-provider peering link ? 159/10000 · 159 Needs editing
11 ../../exercises/routing-policies.rst:133
	English Consider the network below in which a stub domain, `AS456`, is connected to two providers `AS123` and `AS789`. `AS456` advertises its prefix to both its providers. On the other hand, `AS123` advertises ``2001:db8:dead::/48`` while `AS789` advertises ``2001:db8:beef::/48`` and ``2001:db8:dead:cafe::/63``. Via which provider will the packets destined to ``2001:db8:dead:cafe::1`` will be received by `AS456` ?
	English Consider the network below in which a stub domain, `AS456`, is connected to two providers `AS123` and `AS789`. `AS456` advertises its prefix to both its providers. On the other hand, `AS123` advertises ``2001:db8:dead::/48`` while `AS789` advertises ``2001:db8:beef::/48`` and ``2001:db8:dead:cafe::/63``. Via which provider will the packets destined to ``2001:db8:dead:cafe::1`` will be received by `AS456` ? Consider the network below in which a stub domain, `AS456`, is connected to two providers `AS123` and `AS789`. `AS456` advertises its prefix to both its providers. On the other hand, `AS123` advertises ``2001:db8:dead::/48`` while `AS789` advertises ``2001:db8:beef::/48`` and ``2001:db8:dead:cafe::/63``. Via which provider will the packets destined to ``2001:db8:dead:cafe::1`` will be received by `AS456` ? 409/10000 · 409 Needs editing
12 ../../exercises/routing-policies.rst:141
	English Should `AS123` change its configuration ?
	English Should `AS123` change its configuration ? Should `AS123` change its configuration ? 41/10000 · 41 Needs editing
13 ../../exercises/routing-policies.rst:143
	English Consider that the AS stub (`AS456`) shown in the figure below decides to advertise two ``/48`` prefixes instead of its allocated ``/47`` prefix.
	English Consider that the AS stub (`AS456`) shown in the figure below decides to advertise two ``/48`` prefixes instead of its allocated ``/47`` prefix. Consider that the AS stub (`AS456`) shown in the figure below decides to advertise two ``/48`` prefixes instead of its allocated ``/47`` prefix. 144/10000 · 144 Needs editing
14 ../../exercises/routing-policies.rst:151
	English Via which provider does `AS456` receive the packets destined to ``2001:db8:caff::bb`` and ``2001:db8:cafe::aa`` ?
	English Via which provider does `AS456` receive the packets destined to ``2001:db8:caff::bb`` and ``2001:db8:cafe::aa`` ? Via which provider does `AS456` receive the packets destined to ``2001:db8:caff::bb`` and ``2001:db8:cafe::aa`` ? 113/10000 · 113 Needs editing
15 ../../exercises/routing-policies.rst:153
	English How is the reachability of these addresses affected when link `R1`-`R3` fails ?
	English How is the reachability of these addresses affected when link `R1`-`R3` fails ? How is the reachability of these addresses affected when link `R1`-`R3` fails ? 79/10000 · 79 Needs editing
16 ../../exercises/routing-policies.rst:155
	English Propose a configuration on R1 that achieves the same objective as the one shown in the figure but also preserves the reachability of all IP addresses inside `AS456` if one of `AS456`'s interdomain links fails.
	English Propose a configuration on R1 that achieves the same objective as the one shown in the figure but also preserves the reachability of all IP addresses inside `AS456` if one of `AS456`'s interdomain links fails. Propose a configuration on R1 that achieves the same objective as the one shown in the figure but also preserves the reachability of all IP addresses inside `AS456` if one of `AS456`'s interdomain links fails. 209/10000 · 209 Needs editing
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.
	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. 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. 424/10000 · 424 Needs editing
18 ../../exercises/routing-policies.rst:163
	English A simple network
	English A simple network A simple network 16/10000 · 16 Needs editing
19 ../../exercises/routing-policies.rst:165
	English On recent routers, a lookup in the forwarding table for a destination address returns a set of outgoing interfaces. How would you design an algorithm that selects the outgoing interface used for each packet, knowing that to avoid reordering, all segments of a given TCP connection should follow the same path ?
	English On recent routers, a lookup in the forwarding table for a destination address returns a set of outgoing interfaces. How would you design an algorithm that selects the outgoing interface used for each packet, knowing that to avoid reordering, all segments of a given TCP connection should follow the same path ? On recent routers, a lookup in the forwarding table for a destination address returns a set of outgoing interfaces. How would you design an algorithm that selects the outgoing interface used for each packet, knowing that to avoid reordering, all segments of a given TCP connection should follow the same path ? 310/10000 · 310 Needs editing
20 ../../exercises/routing-policies.rst:167
	English A ``traceroute6`` towards ``ipv6.google.com`` provides the following output :
	English A ``traceroute6`` towards ``ipv6.google.com`` provides the following output : A ``traceroute6`` towards ``ipv6.google.com`` provides the following output : 77/10000 · 77 Needs editing