Re: ospfd network
On 30/09/12 14:24, Claudio Jeker wrote:
On Sat, Sep 29, 2012 at 03:22:58PM +0300, Kapeatanakis Giannis wrote:
Hi,
I have two questions regarding ospfd.
a) is there an equivalent to Cisco's or Quagga's "network" definition
network 10.0.0.0/24 area 0.0.0.1
in order to define that a certain network belongs to a certain area?
No. The "redistribute foo" in ospfd will generate AS-ext LSA and those are
not bound to an area.
From my understanding of ospfd.conf(5) the only way to do this is to
put the interface definition in area {}.
Maybe I'm missing something.
No that is correct.
b) quagga support ACLs on areas like import-list
Is there a way for filtering out certain route announcements from
remote routers?
No, it is no possible to filter between areas.
Thanks for the clarifications Claudio.
Giannis
Re: ospfd network
On Sat, Sep 29, 2012 at 03:22:58PM +0300, Kapeatanakis Giannis wrote:
> Hi,
>
> I have two questions regarding ospfd.
>
> a) is there an equivalent to Cisco's or Quagga's "network" definition
> network 10.0.0.0/24 area 0.0.0.1
> in order to define that a certain network belongs to a certain area?
No. The "redistribute foo" in ospfd will generate AS-ext LSA and those are
not bound to an area.
> From my understanding of ospfd.conf(5) the only way to do this is to
> put the interface definition in area {}.
> Maybe I'm missing something.
No that is correct.
> b) quagga support ACLs on areas like import-list
> Is there a way for filtering out certain route announcements from
> remote routers?
>
No, it is no possible to filter between areas.
--
:wq Claudio
Re: ospfd : "network" feature to annouce specific routes ?
On 2006/09/30 23:04, Ronnie Garcia wrote: > Stuart Henderson a icrit : > >On 2006/09/30 21:59, Ronnie Garcia wrote: > >>Is it planned at any time to implement a (cisco-like) "network" > >>parameter, to be able to tell ospfd which network it should annouce ? > >> > >>Actually i need a mix of "default" and "static"/"connected" as i would > >>like my border routers (also running bgpd) to announce a default route, > >>and a few static/connected routes into the IGP. > > > >You can have more than one 'redistribute' line. > > Alright, it's just not quite clear in the man page =] > Works well, thanks. This is clearer now (4.0/-current). > >Also did you notice > >'redistribute '? > > This one did not work. > I'm using -stable (3.9) so it might be a new feature ? yes, added at the end of May. rev 1.16 of ospfd.conf(5): "Document all the new and shiny redistribute options" - support for redist (and no-redist) based on route-labels was supported at around the same time too.
Re: ospfd : "network" feature to annouce specific routes ?
On 2006/09/30 21:59, Ronnie Garcia wrote: > Is it planned at any time to implement a (cisco-like) "network" > parameter, to be able to tell ospfd which network it should annouce ? > > Actually i need a mix of "default" and "static"/"connected" as i would > like my border routers (also running bgpd) to announce a default route, > and a few static/connected routes into the IGP. You can have more than one 'redistribute' line. Also did you notice 'redistribute '?
Re: ospfd : "network" feature to annouce specific routes ?
Stuart Henderson a icrit : On 2006/09/30 21:59, Ronnie Garcia wrote: Is it planned at any time to implement a (cisco-like) "network" parameter, to be able to tell ospfd which network it should annouce ? Actually i need a mix of "default" and "static"/"connected" as i would like my border routers (also running bgpd) to announce a default route, and a few static/connected routes into the IGP. You can have more than one 'redistribute' line. Alright, it's just not quite clear in the man page =] Works well, thanks. Also did you notice 'redistribute '? This one did not work. I'm using -stable (3.9) so it might be a new feature ? In ospfd.conf : redistribute X.Y.Z.0/30 /usr/sbin/ospfd gives : /etc/ospfd.conf:10: unknown redistribute type I tryed with several syntaxes, with no luck. Regards, -- Ronnie Garcia
