Re: ospfd: depend on interface (new feature)

2018-04-20 Thread Remi Locherer
On 2018-04-20 15:39, Kapetanakis Giannis wrote: On 20/04/18 16:20, Remi Locherer wrote: On 2018-04-20 14:46, Kapetanakis Giannis wrote: While it does the job for local connected/static networks (on the router), it doesn't do it for forwarded routes which I learn from remote OSPF routers.

Re: ospfd: depend on interface (new feature)

2018-04-20 Thread Kapetanakis Giannis
sorry setup is different: - [OB1]- [Cisco_ext_1] --- [Cisco_int] --| |--- [BGP router] - [OB2]- [Cisco_ext2_ ]--- G

Re: ospfd: depend on interface (new feature)

2018-04-20 Thread Kapetanakis Giannis
On 20/04/18 16:20, Remi Locherer wrote: > On 2018-04-20 14:46, Kapetanakis Giannis wrote: >> While it does the job for local connected/static networks (on the router), >> it doesn't do it for forwarded routes which I learn from remote OSPF routers. > > LSAs from other routers are not changed by

Re: ospfd: depend on interface (new feature)

2018-04-20 Thread Remi Locherer
On 2018-04-20 14:46, Kapetanakis Giannis wrote: On 04/02/18 01:42, Remi Locherer wrote: Hi This adds a new feature to ospfd: depend on interface. A ospfd.conf using it looks like this: --%<-- redistribute default depend on carp0 area 0.0.0.0 { interface em2 { depend on ca

Re: ospfd: depend on interface (new feature)

2018-04-20 Thread Kapetanakis Giannis
On 04/02/18 01:42, Remi Locherer wrote: > Hi > > This adds a new feature to ospfd: depend on interface. > > A ospfd.conf using it looks like this: > > --%<-- > redistribute default depend on carp0 > area 0.0.0.0 { >

Re: ospfd: depend on interface (new feature)

2018-02-04 Thread Stuart Henderson
On 2018/02/04 23:04, Kapetanakis Giannis wrote: > On 04/02/18 17:52, Stuart Henderson wrote: > > On 2018/02/04 02:56, Kapetanakis Giannis wrote: > > > On 04/02/18 01:42, Remi Locherer wrote: > > > > Hi > > > > > > > > This adds a new feat

Re: ospfd: depend on interface (new feature)

2018-02-04 Thread Kapetanakis Giannis
On 04/02/18 17:52, Stuart Henderson wrote: On 2018/02/04 02:56, Kapetanakis Giannis wrote: On 04/02/18 01:42, Remi Locherer wrote: Hi This adds a new feature to ospfd: depend on interface. If I understand this right, someone could use this combined with pfsync, to wait for states full sync

Re: ospfd: depend on interface (new feature)

2018-02-04 Thread Stuart Henderson
On 2018/02/04 02:56, Kapetanakis Giannis wrote: > On 04/02/18 01:42, Remi Locherer wrote: > > Hi > > > > This adds a new feature to ospfd: depend on interface. > > > > A ospfd.conf using it looks like this: > > > > --%<-- > >

Re: ospfd: depend on interface (new feature)

2018-02-04 Thread Remi Locherer
On Sun, Feb 04, 2018 at 05:19:59AM +0100, Claudio Jeker wrote: > On Sun, Feb 04, 2018 at 12:42:22AM +0100, Remi Locherer wrote: > > Hi > > > > This adds a new feature to ospfd: depend on interface. > > > > A ospfd.conf using it looks like this: > > >

Re: ospfd: depend on interface (new feature)

2018-02-03 Thread Sebastian Benoit
Remi Locherer(remi.loche...@relo.ch) on 2018.02.04 00:42:22 +0100: > Hi > > This adds a new feature to ospfd: depend on interface. > > A ospfd.conf using it looks like this: > > --%<-- > redistribute default depend on carp0 > area 0.0.0.0 { >

Re: ospfd: depend on interface (new feature)

2018-02-03 Thread Claudio Jeker
On Sun, Feb 04, 2018 at 12:42:22AM +0100, Remi Locherer wrote: > Hi > > This adds a new feature to ospfd: depend on interface. > > A ospfd.conf using it looks like this: > > --%<-- > redistribute default depend on carp0 > area 0.0.0.0 { >

Re: ospfd: depend on interface (new feature)

2018-02-03 Thread Kapetanakis Giannis
On 04/02/18 01:42, Remi Locherer wrote: Hi This adds a new feature to ospfd: depend on interface. A ospfd.conf using it looks like this: --%<-- redistribute default depend on carp0 area 0.0.0.0 { interface em2 { depend on carp0 } [...] } --%<-- This router would se

ospfd: depend on interface (new feature)

2018-02-03 Thread Remi Locherer
Hi This adds a new feature to ospfd: depend on interface. A ospfd.conf using it looks like this: --%<-- redistribute default depend on carp0 area 0.0.0.0 { interface em2 { depend on carp0 } [...] } --%<-- This router would send out the default route and the em2 n