Combining routes in BIRD OSPF export

[Steve (Telsat Broadband)]

Hi Ondrej,

Thank you very much for the reply; just to confirm if it should look
something like this:

protocol ospf {
	import all;
	export filter {
		ospf_metric1 = 1000;
		if source = RTS_STATIC then accept; else reject;
	};

	stubnet 2001:abcd::/56 { summary; };

	area 0 {
		interface "eth0" {
			cost 5;
			type broadcast;
			hello 10; 
			retransmit 5; 
			wait 40; 
			dead 40;
			authentication none;
		};

		interface "*" {
			cost 1000;
			stub;
		};
	};
}


Cheers.
Steve.


-----Original Message-----
From: owner-bird-users at atrey.karlin.mff.cuni.cz
[mailto:owner-bird-users at atrey.karlin.mff.cuni.cz] On Behalf Of Ondrej
Zajicek
Sent: Friday, 28 February 2014 7:32 AM
To: Steve (Telsat Broadband)
Cc: bird-users at network.cz
Subject: Re: Combining routes in BIRD OSPF export

On Thu, Feb 27, 2014 at 02:18:03PM +1100, Steve (Telsat Broadband) wrote:
> Hi All,
> 
> I have a question which I can't seem to find the answer for.
> 
> We allocate network ranges to our customers (both IPv4 and v6).
> 
> All our v6 ranges (say /64's) get allocated out of a single larger /56 
> block.
> 
> What I want to do is prevent BIRD from picking up the individual /64's 
> assigned to customers and only 'export' the larger '/56' block to OSPF 
> as this is really all that's required.

Use 'stubnet <prefix> { summary; };' OSPF area option.

--
Elen sila lumenn' omentielvo

Ondrej 'SanTiago' Zajicek (email: santiago at 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."