route0/topology/line_03_and_rogue
2019-04-16 00:13:07 +02:00
..
scenario Add README for the BGP hijacking demo 2019-04-15 23:57:23 +02:00
staticd BGP hijack demo conf files 2019-04-15 22:45:43 +02:00
zebra Port remaining files for the BGP hijack demo 2019-04-15 23:33:20 +02:00
__init__.py BGP hijack demo conf files 2019-04-15 22:45:43 +02:00
README.md Add a clarification to the rogue topology README 2019-04-16 00:13:07 +02:00
topo.py BGP hijack demo conf files 2019-04-15 22:45:43 +02:00

Line of three and rogue router topology

 ------        ------        ------
|      |      |      |      |      |
|  R1 4|------|4 R2 5|------|4 R3  |
|  5   |      |      |      |      |
 ------        ------        ------
   |
   |
   |
 ------
|  4   |
|  R4  |
|      |
 ------

There are three hosts connected to each router, but are not displayed in this README. For details see their zebra and staticd configuration files.

The router R4 is rogue and uses the same prefix as R3. Therefore, its zebra daemon is not started automatically. It must be started manually. See the BGP hijack demo for an example.

R1

Interface Name Address/Subnet
0 lo 127.0.0.1/32
1 R1-eth1 11.0.1.254/24
2 R1-eth2 11.0.2.254/24
3 R1-eth3 11.0.3.254/24
4 R1-eth4 9.0.0.1/24
5 R1-eth5 9.0.4.1/24

R2

Interface Name Address/Subnet
0 lo 127.0.0.1/32
1 R2-eth1 12.0.1.254/24
2 R2-eth2 12.0.2.254/24
3 R2-eth3 12.0.3.254/24
4 R2-eth4 9.0.0.2/24
5 R2-eth5 9.0.1.1/24

R3

Interface Name Address/Subnet
0 lo 127.0.0.1/32
1 R3-eth1 13.0.1.254/24
2 R3-eth2 13.0.2.254/24
3 R3-eth3 13.0.3.254/24
4 R3-eth4 9.0.1.2/24

R4

Interface Name Address/Subnet
0 lo 127.0.0.1/32
1 R4-eth1 13.0.1.254/24
2 R4-eth2 13.0.2.254/24
3 R4-eth3 13.0.3.254/24
4 R4-eth4 9.0.4.2/24