Commit 67ae437d by Kévin Vermeulen

Merge branch 'patch-3' into 'master'

Update README.md

See merge request !3
parents cdfda111 12f36b60
# FakeRouteC++
This tool has been developped in order to emulate very lightweight routing logic to test [Paris Traceroute](https://) algorithm on multipaths-detection, see https:// for more information.
This tool has been developped in order to emulate very lightweight routing logic to test [Paris Traceroute](https://paris-traceroute.net/) algorithm on multipaths-detection, see https:// for more information.
## Getting Started
First you need to create your topology:
......@@ -42,7 +42,7 @@ You also need the following C and C++ libraries to be installed :
[libtins](http://libtins.github.io/download/)
[libnetfilter_queue](https://git.netfilter.org/libnetfilter_queue/)
/!\ libnetfilter_queue needs :
/!\ libnetfilter_queue needs /!\:
[libmnl](https://git.netfilter.org/libmnl/)
......@@ -59,7 +59,7 @@ So you need to tap the following commands:
sudo iptables -A OUTPUT -j NFQUEUE -d 127.1.1.6 --queue-num 1
sudo iptables -A OUTPUT -j NFQUEUE -d 127.1.1.1 --queue-num 1
```
The first one redirects output traffic that have 127.1.1.6 as a destination into libnetfilter_queue. So that means that all your topologies that you are going to test must have 127.1.1.6 as destination.
The first one redirects output traffic that have 127.1.1.6 as a destination into libnetfilter_queue. So that means that all your topologies that you are going to test **must have 127.1.1.6 as destination**.
You can change this parameter in fakerouteC__ as it is one of its arguments, but this also means that you have to Remove the iptables rule with 127.1.1.6 and add yours with the other address.
The second command is a trick to reset the flows id of the router if you want to run several independent tests. (See [TestParisTraceroute] for more information)
......@@ -68,12 +68,12 @@ The second command is a trick to reset the flows id of the router if you want to
The tool is built with cmake.
Create a build folder in the fakeroute folder then launch cmake from there:
Create a build folder in the fakeroute directory then launch cmake from there:
```
mkdir fakeroute/build
cd fakeroute/build
mkdir ~/fakeroute/build
cd ~/fakeroute/build
cmake ../
make
```
......@@ -81,25 +81,24 @@ The executable is named fakeRouteC__ and can be found in the build directory.
###Usage
```
./fakerouteC__ <topologyFile> <destination> <queue-number>
fakerouteC__ <topologyFile> <destination> <queue-number>
```
### Break down into end to end tests
To test the tool, you need to have paris-traceroute installed. Then you just have to launch your command and wait for the response to print on the standard output.
In a terminal, tap:
Suppose we are in ~/fakeroute/build, launch this command:
```
sudo ./fakerouteC__ ../resources/2-pathsLoadBalancer 127.1.1.6 1
sudo fakerouteC__ ../resources/2-pathsLoadBalancer 127.1.1.6 1
```
(We suppose that we are on ~/fakeroute/build )
The first argument is the topology file. The second argument is the destination of the traceroute that you want to execute. The third argument is the queue that you have bound in the iptables command.
In another terminal in paris-traceroute folder:
```
sudo ./paris-traceroute -amda -B95,1,128 127.1.1.6
sudo paris-traceroute -amda -B95,1,128 127.1.1.6
```
See paris-traceroute for options meanings.
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment