Exit Zen
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
58
../../exercises/routing-protocols.rst:841
English
the eBGP session with ``fe80::c001:dcff:fe49:a512`` with an AS-Path of ``AS2`` (see last column)
0/960 · 96
59
../../exercises/routing-protocols.rst:843
English
The first of these two routes is preferred as indicated by the `>` character because it has a higher ``local-preference` (150) than the second one (100). For prefix ``2001:cafe:3::/48``, the route learned via ``fe80::3c81:2eff:fe19:465d`` is also preferred for the same reason.
0/2770 · 277
60
../../exercises/routing-protocols.rst:845
English
IPMininet_ also allows to explore the dynamics of BGP by looking at the packets that the routers exchange. For this, we slightly modify the example above and add delays to the interdomain links as follows.
0/2050 · 205
61
../../exercises/routing-protocols.rst:854
English
We also add a ``post_build`` method to launch tcpdump_ and capture the BGP packets exchanged by the routers. A BGP session runs over a TCP connection. Let us examine a few of the BGP messages exchanged on the BGP session between ``AS1`` and ``AS2``. The traces collected on the three routers are available from :download:`/exercises/traces/bgp-as1-trace.pcap`, :download:`/exercises/traces/bgp-as2-trace.pcap` and :download:`/exercises/traces/bgp-as2-trace.pcap`.
0/4630 · 463
62
../../exercises/routing-protocols.rst:856
English
The BGP session starts with a TCP three-way handshake. Once the session has been established, both BGP daemons send an ``OPEN`` message describing their capabilities and the BGP extensions that it supports. The details of these extensions go beyond the scope of this book. However, it is important to note that the ``OPEN`` message contains the ``AS`` number of the router that sends the message and its identifier as a 32 bits IPv4 address. This router identifier uniquely identifies the router. The last mandatory parameter of the ``OPEN`` message is the `Hold Time`, i.e. the maximum delay between two successive messages over this BGP session. A BGP router should send ``KEEPALIVE`` messages every one third of the `Hold Time` to keep the session up.
0/7540 · 754