Hello!
I just started working on a patch that adds export filters and the
"table" action as Juliusz suggested.
Jernej
On 03. 09. 2015 06:32, Mitar wrote:
> Hi!
>
> Any progress on this? I know that not yet many days have passed, but
> it is pretty urgent for us, because the network grew to
> I just started working on a patch that adds export filters and the
> "table" action as Juliusz suggested.
Arf, sorry, I was also doing one (attached).
Matthieu
0001-Add-filter-to-choose-the-export-routing-table.patch
Description: Binary data
___
Hi!
Any progress on this? I know that not yet many days have passed, but
it is pretty urgent for us, because the network grew to the stage
where OLSR routing is unstable so we would need to switch to Babel as
soon as possible.
Mitar
On Thu, Aug 27, 2015 at 9:03 AM, Jernej Kos
The default route into its own table is used for more complex setups
where you have different kinds of internet uplinks (e.g. the normal
one for your traffic, a VPN for mesh traffic)
We solved that particular problem in our network with source-specific
routing.
or where you don't want
to
Why not having a separate service which duplicates the routes you want
into the tables you want?
I think it's much cleaner to add filtering at the export stage. Something
like
export ip :: le 0 table 42
-- Juliusz
___
Babel-users mailing list
Yes,
copying the routes with a second service just to put some of them into
a different routing table sounds like a lot of unnecessary complexity.
Henning
On Thu, Aug 27, 2015 at 3:16 PM, Juliusz Chroboczek
j...@pps.univ-paris-diderot.fr wrote:
Why not having a separate service which
On Thu, Aug 27, 2015 at 12:49 AM, Juliusz Chroboczek
j...@pps.univ-paris-diderot.fr wrote:
Then we can have the following order of routing tables on routers:
babel
olsr
babel_default
olsr_default
Mitar,
I'll be glad to implement the hack that you require, but let's please
think whether
Hi!
I think that putting routes of both routing protocols in the same
table gets really messy and hard to debug. And prevents any policy
routing rules we might want to apply.
Mitar
On Wed, Aug 26, 2015 at 3:49 PM, Juliusz Chroboczek
j...@pps.univ-paris-diderot.fr wrote:
Then we can have the
Hello!
Is it possible to specify the routing table of exported routes in
babeld? So for example that the default route would be put into a
separate routing table from the other exported routes?
Jernej
signature.asc
Description: OpenPGP digital signature
Hello!
Yes, but this applies to all routes. I would like to export the default
route to a different routing table than all the other routes.
Jernej
On 26. 08. 2015 23:49, max b wrote:
The `-t` flag allows you to specify a table you'd like to export routes to,
or in the config file:
Hi!
Just to give a bit of background, we need this to be able to run
multiple routing protocols at the same time. This allows us to
gradually transition to a new routing protocol (Babel). Then we can
have the following order of routing tables on routers:
babel
olsr
babel_default
olsr_default
Then we can have the following order of routing tables on routers:
babel
olsr
babel_default
olsr_default
Mitar,
I'll be glad to implement the hack that you require, but let's please
think whether we can manage to avoid it. What's wrong with putting both
OLSR and Babel routes into a
12 matches
Mail list logo