You wrote:
On Thu, Jul 24, 1997 at 04:49:29PM -0700, J.D. Falk wrote:
But, seperate real ASN or seperate community, you'll still want to filter incoming announcements from the customer -- just as they'd probably want to filter announcements from you.
I think you mean confederation, JD.
Alec
--
Don't think he did, Alec. Using communities would make it much easier to filter the routes to the customer than using confederation. I don't think there's any need to implement confedrations here. Sounds like headaches I don't need. Communities would allow you to filter very specifically only routes coming from the router. The real problem here is that the ISP with the EBGP session still depends on the ISP with the IBGP session to do things correctly, unless customer routes are filtered at a network level -- Something I've never liked doing, but always felt was necessary. How can I have a setup that is flexible enough to satisfy my customer (and my workload) but safe for me? I've had customers running OSPF with one of my routers that was redistributing OSPF into BGP, and it was probably one of the stupidest mistakes I've ever made. Screwed me when some dumbass decided he could use whatever networks he wanted on the Sun they were running gated on.
+------------------------------------+--------------------------------------+
|Alec Peterson - ahp@hilander.com | Erols Internet Services, INC. | |Network Engineer | Springfield, VA. |
+------------------------------------+--------------------------------------+ --- -=<:gEm:>=- -<sMp>-<sMp>-<sMp>-<sMp>-<sMp>-<sMp>-<sMp>-<sMp>-<sMp>-- Gordon Mercer -=<Dedicated>=- [digitalNATION] 703 642 2800 -=<Servers>=- gmercer@dn.net <::>=-=<::>=--=<::>=-=<::>=--=<::>=-=<::>=--=<::>=-=<::>