Re: OSPF and Assigned Address Pool (fwd)

Jon Lewis (jlewis@inorganic5.fdt.net)
Mon, 12 May 1997 23:48:05 -0400 (EDT)

On Mon, 12 May 1997, MegaZone wrote:

> It has an algorithm for determining the least number of routes needed to
> cover the pool. Personally I think that's pretty slick...

Slick or sick?

205.229.60.1 205.229.48.10 255.255.255.255 UGH 0 0 0 eth0
205.229.60.2 205.229.48.10 255.255.255.254 UG 0 0 25 eth0
205.229.60.4 205.229.48.10 255.255.255.252 UG 0 0 1 eth0
205.229.60.8 205.229.48.10 255.255.255.248 UG 0 0 0 eth0
205.229.60.16 205.229.48.10 255.255.255.248 UG 0 0 19 eth0
205.229.60.24 205.229.48.10 255.255.255.252 UG 0 0 4 eth0
205.229.60.28 205.229.48.10 255.255.255.254 UG 0 0 0 eth0
205.229.60.30 205.229.48.10 255.255.255.255 UGH 0 0 2 eth0

If this were gated, I'd

static {
205.229.60.0 masklen 27 gateway 127.0.0.1 preference 200 reject;
} ;
export proto ospfase type 2 {
proto direct {
205.229.60.0 masklen 27 refines restrict;
};
proto static;
};

and export only one route.

------------------------------------------------------------------
Jon Lewis <jlewis@fdt.net> | Unsolicited commercial e-mail will
Network Administrator | be proof-read for $199/hr.
________Finger jlewis@inorganic5.fdt.net for PGP public key_______