Very simple bird.conf

[Ondrej Zajicek]

On Wed, Apr 14, 2010 at 07:09:17PM +0200, Ondrej Filip wrote:
> > 
> > Yes, would replacing direct { } with
> > 
> >   static {
> >     route 0.0.0.0/0 via 84.45.39.149;
> >     route 91.203.56.0/23 via "eth0";
> >   }
> > 
> > be more idiomatic here?

The second route has one side-effect - it is exported to the kernel
as a device route. If you really have prefix 91.203.56.0/23 on eth0,
it is definitely better to use direct route, if 91.203.56.0/23 is an
aggregate of your internal routes, i would suggest to use drop route
(route XXXX/YY drop), as suggested by Ondrej Filip. The drop route
is also exported to the kernel routing table, which has a slight
benefit that every destination (from XXXX/YY) that is not covered
by more specific (IGP) route is dropped and not send through the
default route.

-- 
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."
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
URL: <http://trubka.network.cz/pipermail/bird-users/attachments/20100414/5a77b4ee/attachment-0001.asc>