No comment, just try bigger hammers. I'm not gonna write a rant about
how openvswitch in Debian is mostly broken always regarding
network/interfaces handling. It's like playing whack a mole.
Argh, if everything is OK the script wouldn't generate any output, which
is also confusing.
So, just show everything that is happening... The amount of routers in
the example is not that big.
The first thing I did in this assignment is disabled connection
R1-R20. And spend some time trying to understand how it is even
supposed to work, before I scrolled down and read that it is not
supposed actually.
So let's not ask a person to check if he can reach ALL parts of the
network, but only reasonable for now parts.
Edit by Knorrie:
* Explicitely mention what can be disabled now, so that we don't run
into the situation above. :)
Add a script for testing connectivity. Basically ping every router
from every router.
Edit by Knorrie:
* Ignore all the crap that ping outputs
* Test all links, don't stop when one fails.
* Insert commented out extra [OK] output that can be enabled quickly to
also see all connections that succeed
It was a bit unclear for me, what to do with fixnetwork.sh
script. This modifications should help to avoid confusion
Edit by Knorrie:
* Fix up some whitespace
* Make fixnetwork executable, it already had a shebang
* Copy both router and host files, if present: [RH]*
lxc-clone is not available anymore. From lxc-copy man:
> lxc-copy creates and optionally starts (ephemeral or non-ephemeral)
> copies of existing containers. It replaces lxc-clone and
> lxc-start-ephemeral.
When swapping the place of R10 and R11, traffic flow between AS65000 and
AS65010 will be asymmetric by default. It's nice to be able to show this
when introducing the possibility of traffic taking multiple paths.
iperf3 can be used to send data fast or slow over a TCP connection,
detecting packet loss. We'll be using it in the tutorials to show that
it's possible to fail over routes dynamically without any loss of
connectivity.
