From kurt at max.wcom-dsl.de Wed Oct 1 15:03:55 2003 From: kurt at max.wcom-dsl.de (kurt at max.wcom-dsl.de) Date: Wed, 1 Oct 2003 15:03:55 +0200 Subject: N-IX installed 3 root nameservers In-Reply-To: <200309261427.h8QERTgF024139@birch.ripe.net>; from carsten@ripe.net on Fri, Sep 26, 2003 at 04:27:29PM +0200 References: <200309261427.h8QERTgF024139@birch.ripe.net> Message-ID: <20031001150355.A13602@max2.araponga.de> Hi, I just wanted to inform the RIPE community that we (teamix) colocated a Serversetup at the N-IX (N?rnberg Internet eXchange) with a redirection of the three most distant Root-Nameserver, thus are: E.ROOT-SERVERS.NET - Nasa Ames, California, USA L.ROOT-SERVERS.NET - ICANN, California, USA M.ROOT-SERVERS.NET - Tokyo, JP We thought it makes most sense for all connected networks to reach three out of 13 Servers with a *very* good response time. You are highly invited to request more information about our operations team. Best regards, Kurt Kayser -- + Kurt Kayser - Gesch?ftsf?hrer Netzwerke - teamix GmbH + * S?dwestpark 35, 90449 N?rnberg, Germany (Old Europe) * # Tel: +49 911 30 999 0, Mobil: +49 160 5810284 # From he at uninett.no Thu Oct 2 10:10:51 2003 From: he at uninett.no (Havard Eidnes) Date: Thu, 02 Oct 2003 10:10:51 +0200 (CEST) Subject: bgp behavior with exchange prefix in ebgp In-Reply-To: <20030905102422.Z67740@Space.Net> References: <91BBE3F7-DF79-11D7-A55A-00039388672E@muada.com> <20030905102422.Z67740@Space.Net> Message-ID: <20031002.101051.93858625.he@uninett.no> I know -- catching up on old e-mail... > On Fri, Sep 05, 2003 at 10:18:45AM +0200, Iljitsch van Beijnum wrote: > > Note that the next hop points to an address that falls within the (old) > > AMS-IX peering LAN prefix. Since this router isn't directly connected > > to the AMS-IX, it needs to resolve this next hop: > > Two ways to remedy this: > > - use next-hop-self on all iBGP peerings (which isn't always the > perfect choice, but will easily fix these issues) > > - filter the exchange prefix(es) for all IXes that you participate *and > all more specifics* on *all* eBGP sessions. This is strongly recommended > even when already using next-hop-self (more specifics can break eBGP > sessions at the IXP peering routers) A third and additional defensive measure could be to adjust the preference of your IGP to a value below that for eBGP, and do the moral equivalent of "redistribute connected" on the exchange point router into your IGP. Regards, - H?vard From gert at space.net Thu Oct 2 10:13:54 2003 From: gert at space.net (Gert Doering) Date: Thu, 2 Oct 2003 10:13:54 +0200 Subject: bgp behavior with exchange prefix in ebgp In-Reply-To: <20031002.101051.93858625.he@uninett.no>; from he@uninett.no on Thu, Oct 02, 2003 at 10:10:51AM +0200 References: <91BBE3F7-DF79-11D7-A55A-00039388672E@muada.com> <20030905102422.Z67740@Space.Net> <20031002.101051.93858625.he@uninett.no> Message-ID: <20031002101354.I67740@Space.Net> Hi, On Thu, Oct 02, 2003 at 10:10:51AM +0200, Havard Eidnes wrote: > > - filter the exchange prefix(es) for all IXes that you participate *and > > all more specifics* on *all* eBGP sessions. This is strongly recommended > > even when already using next-hop-self (more specifics can break eBGP > > sessions at the IXP peering routers) > > A third and additional defensive measure could be to adjust the > preference of your IGP to a value below that for eBGP, and do the > moral equivalent of "redistribute connected" on the exchange > point router into your IGP. While I agree that it's useful, it still needs measure 2 - the problem being more-specific annonucements of the IXP prefixes (which can't be caught by the IGP<->BGP preference). Gert Doering -- NetMaster -- Total number of prefixes smaller than registry allocations: 56883 (56833) SpaceNet AG Mail: netmaster at Space.Net Joseph-Dollinger-Bogen 14 Tel : +49-89-32356-0 80807 Muenchen Fax : +49-89-32356-299 From randy at psg.com Thu Oct 2 15:45:45 2003 From: randy at psg.com (Randy Bush) Date: Thu, 2 Oct 2003 06:45:45 -0700 Subject: bgp behavior with exchange prefix in ebgp References: <91BBE3F7-DF79-11D7-A55A-00039388672E@muada.com> <20030905102422.Z67740@Space.Net> <20031002.101051.93858625.he@uninett.no> Message-ID: you may find http://www.acm.org/sigcomm/sigcomm2002/papers/ibgp.html interesting randy