[175854] in North American Network Operators' Group
Re: Default routes on BGP routers with full feeds
daemon@ATHENA.MIT.EDU (Mark Tinka)
Wed Nov 5 00:50:17 2014
X-Original-To: nanog@nanog.org
From: Mark Tinka <mark.tinka@seacom.mu>
To: nanog@nanog.org
Date: Wed, 5 Nov 2014 07:50:03 +0200
In-Reply-To: <20141104174738.70B382D4328@mail.nanog.org>
Reply-To: mark.tinka@seacom.mu
Errors-To: nanog-bounces@nanog.org
--nextPart4184615.AffORQ4Fq0
Content-Type: Text/Plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
On Tuesday, November 04, 2014 07:47:21 PM Berry Mobley=20
wrote:
> I'm wondering how many of you who are multihomed also add
> default routes pointing to your providers from whom you
> are receiving full feeds.
>=20
> If so, why? If not, why not?
We filter out default routes from our upstreams, but many of=20
our customers request it so we send them both full + default=20
routes.
We have not yet been in a position where a default route to=20
an upstream would have come in handy, as we do a lot of=20
peering (close to 70% of our Internet traffic) and have a=20
reasonable number of upstreams.
Mark.
--nextPart4184615.AffORQ4Fq0
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (GNU/Linux)
iQIcBAABAgAGBQJUWbqMAAoJEGcZuYTeKm+GfhcP/Am7FD7Y0Smvud1HEqM4fgb8
4M4XuDNlIB6TIR3aqGIKd/muu5AgdEGXQl+5+EgEZ+O45aFWrLJeVVs+P5Bo5n0h
Et2qgAvhXE5RzMd3LwlCKmMNhZMUMehgbhSID94hhtiG5WoVDzr+rgKzjWugk1nb
4/0ak402eJbI9viDGCu3LDuCtVu8TlpHUDsXE/5cGUdpNMFTanHaqeIRKPx9sCwY
sdWq3XI06A5sZV8ET57sNS7KwCjJZ6QF0+k5gtZP2edfHcTS6BW6XCVvfNRlUP27
ckjfLGvydbhjDKYuQLNqivw538sJZPcQvPIrhLKIhqdnIGtTCjPmYzi/8nRKYmiQ
KOM8ZwSUv1Oh01g9NxFB4ovKrZbaVHXWJOGNii+a3oJ0zvWMbeL/pu0H80Qeaqpz
mE9qVp/3GU2yAHaWEhUx4CNM5z6gsaeJIJeqe2IpL5jSneOF5HfnkDImUYMCKpZ6
jNtFnY3VAJpL479te3uZ2OM8sXfSn9iZcAP4gq08Kg4BGZhFRZdWp8qY6oH9659U
KLAm+RF2NlwxofRluEUOWKPRbRfLvWaHVVCIbVnxuLVum4UtmtarEEzP7UchagJ5
Mm39eU1xzHUARn4D8eIdGzwJgWBGi5bN55U0vwVN8DBkzSbL8s5lsyxy76EtS5DT
kqY0CcH5dAvkIvg7P+EW
=hPiw
-----END PGP SIGNATURE-----
--nextPart4184615.AffORQ4Fq0--
