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.
23:41 < Elrond> Knorrie - 2. On exporting routes from bgp to ospf: If
your network is complex enough, you will start to deploy router more
deeply inside your structure, and those will only know ospf. So having
some E1/E2 big routes exported into ospf is often used there. So those
networks get the traffic out to some router that knows better and
probably has the specific bgp routes in it.
23:42 < Knorrie> aha
23:42 < Knorrie> good point
23:43 < Knorrie> so in the ospf-only segment, there is no reason to do
intelligent things with the information, just get it into the right
direction
23:44 < Elrond> Yeah.
23:45 < Knorrie> so I can change it from: "this is baaaaad, never do
this" to a bit more soft wording
23:45 < Elrond> Think buildings far away from your main
big-network-computer-centre. Those might have redundant links to your
main building. But that's handled by ospf, nicely. You just need to get
the traffic to the main building.
23:45 < Knorrie> I get it yes
23:46 < Elrond> I am not 100% sure it's done like this by many people,
though.
23:46 < Elrond> And I would not export the whole bgp-table into ospf.
Just aggregates. In the worst case, export a 0/0 into ospf.
23:47 < Elrond> More specific routes will always win, you know.
