I saw a recent post about combining routes in OSPF and wanted the answer to the BGP version of the question. I have a /24 split into several subnets on my BGP speaking box. I only want to export the /24. On quagga or cisco I'd use a "network" statement.
On Thu, Mar 06, 2014 at 08:08:20PM +1300, Andy Linton wrote:
I saw a recent post about combining routes in OSPF and wanted the answer to the BGP version of the question.
I have a /24 split into several subnets on my BGP speaking box. I only want to export the /24.
On quagga or cisco I'd use a "network" statement.
Usual solution is to use static route with that prefix. See this example: https://gitlab.labs.nic.cz/labs/bird/wikis/BGP_example_1 -- Elen sila lumenn' omentielvo Ondrej 'SanTiago' Zajicek (email: santiago@crfreenet.org) OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net) "To err is human -- to blame it on a computer is even more so."
Hi. Also you can use: protocol static { #Our Aggregated prefix route 1.2.3.0/24 drop; } filter out { if (source = RTS_STATIC) && (net = 1.2.3.0/24) then { accept "OUT: Announce our Aggregated pref ", net; } reject; } protocol bgp { ...skiped.... export filter OUT; ...skiped... } -- With best regards, Dmitry S. Nikolaev Moscow, Russia mail: dnikolaev@mega-net.ru On 26.03.2014 00:54, Ondrej Zajicek wrote:
On Thu, Mar 06, 2014 at 08:08:20PM +1300, Andy Linton wrote:
I saw a recent post about combining routes in OSPF and wanted the answer to the BGP version of the question.
I have a /24 split into several subnets on my BGP speaking box. I only want to export the /24.
On quagga or cisco I'd use a "network" statement. Usual solution is to use static route with that prefix. See this example:
Hi all, is this aggregation method also to be used for OSPF (outgoing an interface in area 0.0.0.0)? thx for your advise Ar From: "Dmitry S. Nikolaev" <dnikolaev@mega-net.ru> To: Andy Linton <asjl@lpnz.org>, Cc: bird-users@network.cz Date: 26.03.2014 05:36 Subject: Re: Combining routes in BIRD BGP export Sent by: owner-bird-users@atrey.karlin.mff.cuni.cz Hi. Also you can use: protocol static { #Our Aggregated prefix route 1.2.3.0/24 drop; } filter out { if (source = RTS_STATIC) && (net = 1.2.3.0/24) then { accept "OUT: Announce our Aggregated pref ", net; } reject; } protocol bgp { ...skiped.... export filter OUT; ...skiped... } -- With best regards, Dmitry S. Nikolaev Moscow, Russia mail: dnikolaev@mega-net.ru On 26.03.2014 00:54, Ondrej Zajicek wrote:
On Thu, Mar 06, 2014 at 08:08:20PM +1300, Andy Linton wrote:
I saw a recent post about combining routes in OSPF and wanted the answer to the BGP version of the question.
I have a /24 split into several subnets on my BGP speaking box. I only want to export the /24.
On quagga or cisco I'd use a "network" statement. Usual solution is to use static route with that prefix. See this example:
****************************************************** Notice: The information contained in this message is intended only for use of the individual(s) named above and may contain confidential, proprietary or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you are not the intended recipient of this message you are hereby notified that you must not use, disseminate , copy it in any form or take any action in reliance of it. If you have received this message in error please delete it and any copies of it and notify the sender immediately. *******************************************************
Hi. Yes, why not. filter ospfOUT { if (source = RTS_STATIC) && (net = 1.2.3.0/24) then { accept "ospfOUT: Send our Aggregated pref ", net; } reject; } protocol ospf { ...skiped.... area 0.0.0.0 { ...skiped.... }; import filter ospfIN; export filter ospfOUT; } --- With best regards, Dmitry S. Nikolaev Moscow, Russia mail: dnikolaev@mega-net.ru On 26.03.2014 10:50, arno.odermatt@ch.schindler.com wrote:
Hi all,
is this aggregation method also to be used for OSPF (outgoing an interface in area 0.0.0.0)?
thx for your advise
Ar
From: "Dmitry S. Nikolaev" <dnikolaev@mega-net.ru> To: Andy Linton <asjl@lpnz.org>, Cc: bird-users@network.cz Date: 26.03.2014 05:36 Subject: Re: Combining routes in BIRD BGP export Sent by: owner-bird-users@atrey.karlin.mff.cuni.cz ------------------------------------------------------------------------
Hi.
Also you can use: protocol static { #Our Aggregated prefix route 1.2.3.0/24 drop; }
filter out { if (source = RTS_STATIC) && (net = 1.2.3.0/24) then { accept "OUT: Announce our Aggregated pref ", net; } reject; }
protocol bgp { ...skiped.... export filter OUT; ...skiped... }
-- With best regards, Dmitry S. Nikolaev
Moscow, Russia mail: dnikolaev@mega-net.ru
On 26.03.2014 00:54, Ondrej Zajicek wrote:
On Thu, Mar 06, 2014 at 08:08:20PM +1300, Andy Linton wrote:
I saw a recent post about combining routes in OSPF and wanted the answer to the BGP version of the question.
I have a /24 split into several subnets on my BGP speaking box. I only want to export the /24.
On quagga or cisco I'd use a "network" statement. Usual solution is to use static route with that prefix. See this example:
****************************************************** Notice: The information contained in this message is intended only for use of the individual(s) named above and may contain confidential, proprietary or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you are not the intended recipient of this message you are hereby notified that you must not use, disseminate , copy it in any form or take any action in reliance of it. If you have received this message in error please delete it and any copies of it and notify the sender immediately. *******************************************************
participants (4)
-
Andy Linton -
arno.odermatt＠ch.schindler.com -
Dmitry S. Nikolaev -
Ondrej Zajicek