Exit Zen
38
../../exercises/routing-protocols.rst:438
English
``AS3`` is assigned ``2001:cafe:3::/48``
0/400 · 40
39
../../exercises/routing-protocols.rst:454
English
The `addDaemon` method adds a BGP daemon on each router and configures it to advertise the IPv6 prefix allocated to this AS. We then create all the links and manually assign one IPv6 subnet to each link and one IPv6 address to each interface. For the interdomain links, we use an IPv6 prefix that belongs to one of the attached ASes.
0/3330 · 333
40
../../exercises/routing-protocols.rst:491
English
The last step is to specify to which AS each router belongs and to configure the eBGP sessions and their routing policies. IPMininet_ abstracts most of the complexity of the configuration of these policies by supporting two policies
0/2320 · 232
41
../../exercises/routing-protocols.rst:510
English
The script ends by launching the full topology. The entire script is available from :download:`/exercises/ipmininet_scripts/ebgp-simple.py`.
0/1400 · 140
42
../../exercises/routing-protocols.rst:512
English
We can now run this simple network.
0/350 · 35
43
../../exercises/routing-protocols.rst:518
English
If you launch the script and immediately type ``ping6all`` to check the connectivity, you might obtained the following result.
0/1260 · 126
44
../../exercises/routing-protocols.rst:529
English
Remember that BGP is a distributed protocol and that it takes some time to launch the daemons and exchange the messages. After some time, the same command will confirm that everything works as expected.
0/2020 · 202
45
../../exercises/routing-protocols.rst:540
English
We can also use :manpage:`traceroute6(8)` to check the path followed by the packets. Before doing that, think about the configuration of the BGP routing policies and try to predict the output of :manpage:`traceroute6(8)`. This is a good exercise to check your understanding of BGP.
0/2810 · 281
46
../../exercises/routing-protocols.rst:542
English
We have configured the following addresses on the hosts.
0/560 · 56
47
../../exercises/routing-protocols.rst:559
English
We can now explore the routes in this small Internet. Host ``h1`` can reach directly host ``h3``.
0/970 · 97
48
../../exercises/routing-protocols.rst:569
English
Note that the path preferred by ``AS3`` to reach ``AS1`` is different.
0/700 · 70
49
../../exercises/routing-protocols.rst:581
English
The same applies for the paths between ``h1`` and ``h2``
0/560 · 56
50
../../exercises/routing-protocols.rst:598
English
Besides :manpage:`ping6(8)` and :manpage:`traceroute6(8)`, it is also useful to interact with the BGP daemon that runs on each of our routers. This is done by connecting on the Command Line Interface of the BGP router using telnet.
0/2310 · 231
51
../../exercises/routing-protocols.rst:619
English
The password for the BGP daemon is `zebra`. The `noecho` command indicates that mininet_ does not need to echo the characters that you type. You then enter the Quagga VTY that enables you to type commands. The `help` commands gives you some information about the available commands as well as `?`.
0/2970 · 297
52
../../exercises/routing-protocols.rst:649
English
In these exercises, we mainly consider the ``show`` that extracts information from the BGP daemon. We type `show bgp` and press the `tabulation` key to see the available commands in the `show bgp`.
0/1970 · 197
53
../../exercises/routing-protocols.rst:663
English
A useful command to start is `show bgp summary` which provides a summary of the state of the BGP daemon.
0/1040 · 104
54
../../exercises/routing-protocols.rst:685
English
This router (`as1`) has two BGP neighbors: ``2001:cafe:1:12::2`` and ``2001:cafe:1:13::3``. Both BGP sessions are established using the current version of the protocol (version 4). About 50 messages were sent/received over each session. These messages are mainly the BGP Keepalive messages that are exchanged every 30 seconds. The last column indicates that two prefixes were received over each session. We can see more details about these two eBGP sessions with the `show bgp neighbors` command.
0/4960 · 496
55
../../exercises/routing-protocols.rst:812
English
We can now observe the BGP-Loc-RIB of the router with the ``show bgp ipv6 command`` command.
0/920 · 92
56
../../exercises/routing-protocols.rst:838
English
It is interesting to look at the output of this command in details. Router `as1` has routes for three different IPv6 prefixes. The first prefix is its own prefix, ``2001:cafe:1::/48``. It has no nexthop since this prefix is originated by the router. Then, `as1` has received two paths for ``2001:cafe:2::/48``. In the BGP Loc-RIB, the `>` character indicates the best route according to the BGP decision process. ``2001:cafe:2::/48`` was learned over two different BGP sessions:
0/4790 · 479
57
../../exercises/routing-protocols.rst:840
English
the eBGP session with ``fe80::3c81:2eff:fe19:465d`` with an AS-Path of ``AS3:AS2`` (see last column)
0/1000 · 100