[55485] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: routing between provider edge and CPE routers

daemon@ATHENA.MIT.EDU (E.B. Dreger)
Wed Jan 29 15:20:44 2003

Date: Wed, 29 Jan 2003 20:15:41 +0000 (GMT)
From: "E.B. Dreger" <eddy+public+spam@noc.everquick.net>
To: nanog@merit.edu
In-Reply-To: <7CD4CD9D537C294D9ED9E5CE2F019106B6BC4A@MAILSERV.linc2icn.net>
Errors-To: owner-nanog-outgoing@merit.edu


MB> Date: Wed, 29 Jan 2003 12:51:08 -0600
MB> From: Mike Bernico

[ snipped and reformatted throughout ]


MB> We currently use an IGP to route between our distribution
MB> routers and the CPE routers we manage.

I hope I'm misreading.  If you're, say, running OSPF between
your edge routers and CPE routers...


MB> This is causing some problems with stability in that edge
MB> IGP.

...I'd imagine so.

Routes within one administrative domain that are preferred over
BGP routes.  Yikes.  Roguecasting of GTLDs comes to mind as but
one way to do evil deeds.


MB> Does any other service provider use an IGP all the way to the
MB> customer for non BGP customers or are we the only one?  I
MB> have a feeling we maybe are.

Anything that depends on proper configuration of customer gear
is inherently evil and dangerous.  Of course, nobody ever creates
an ethernet loop, redistributes the wrong prefixes, binds the
wrong IP address, or anything like that, right?

Hopefully I misread.  Sharing your IGP with customers is very,
very bad.  Dynamic routes also need to be filtered at untrusted
boundaries.


Eddy
--
Brotsman & Dreger, Inc. - EverQuick Internet Division
Bandwidth, consulting, e-commerce, hosting, and network building
Phone: +1 (785) 865-5885 Lawrence and [inter]national
Phone: +1 (316) 794-8922 Wichita

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Date: Mon, 21 May 2001 11:23:58 +0000 (GMT)
From: A Trap <blacklist@brics.com>
To: blacklist@brics.com
Subject: Please ignore this portion of my mail signature.

These last few lines are a trap for address-harvesting spambots.
Do NOT send mail to <blacklist@brics.com>, or you are likely to
be blocked.


home help back first fref pref prev next nref lref last post