-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I think this is a personal thing. I much prefer the
Juniper model of having all policy in one place. One of
the questions we get asked most often on the courses is
how to inject routes into BGP. Students have a few problems
coming to terms with the lack of a network statement
equivalent.
Dave Humphrey
- -----Original Message-----
From: Jared Mauch [mailto:jared@puck.nether.net]
Sent: 08 September 2001 00:52
To: Paul Traina
Cc: Jared Mauch; Hitesh Patel; 'Przemyslaw Karwasiecki ';
juniper-nsp@puck.nether.net
Subject: Re: [j-nsp] OSPF default information originate?
<insert disclaimer about this not being the opinion of my
employer but my own personal opinion>
It is nice to have a single per-peer configuration option for
bgp (at least) to allow the routing software to generate a default
route
when talking to an ebgp peer. This makes the router configuration
slightly easier for those that are going from an
environment with mostly IOS based devices to JunOS based
devices.
The ease of configuraiton is all my statement is meant
to reflect, in that you could add one or two lines to
the config instead of creating a specific route generation
and policy to handle that route to allow it to go to the
neighbors (ospf+bgp) that one desires.
- Jared
On Fri, Sep 07, 2001 at 04:41:32PM -0700, Paul Traina wrote:
> Why?
>
> > IMHO it's not the most ideal solution but it does work.
>
- --
Jared Mauch | pgp key available via finger from
jared@puck.nether.net
clue++; | http://puck.nether.net/~jared/ My statements are only
mine.
-----BEGIN PGP SIGNATURE-----
Version: PGP 7.0.4
iQA/AwUBO5xyntDzf3p4iWAnEQI7fwCgtQ/ekt1w3SzjwpEHih1UoGy7xdcAnAoU
BHS5xeKHrwowFsM+viBk4lMg
=hcrC
-----END PGP SIGNATURE-----
This archive was generated by hypermail 2b29 : Mon Aug 05 2002 - 10:42:37 EDT