Re: BGP multihoming with two address spaces

2014-01-29 Thread Michael Hallgren
Le 29/01/2014 20:34, Owen DeLong a écrit : >> This sort of local-pref default seems to be a common practice with >> backbones. It's very annoying. I wish they'd stop. > Most of their customers would actually be very unhappy if they stopped. This > local-pref default prevents many many problems and

Re: BGP multihoming with two address spaces

2014-01-29 Thread Owen DeLong
> This sort of local-pref default seems to be a common practice with > backbones. It's very annoying. I wish they'd stop. Most of their customers would actually be very unhappy if they stopped. This local-pref default prevents many many problems and in the vast majority of cases provides the des

Re: BGP multihoming with two address spaces

2014-01-29 Thread William Herrin
On Wed, Jan 29, 2014 at 6:32 AM, Joseph Jenkins wrote: > I am seeking some feedback/help with my BGP configuration. > I am peering with two providers level3 and tw. Unfortunately all of > my address spaces are preferring the route over tw rather than level3. Hi Joe, I had a situation like this

Re: BGP multihoming with two address spaces

2014-01-29 Thread Curtis Doty
According to telnet://route-server.twtelecom.net and http://lookingglass.level3.net/bgp/lg_bgp_main.php BGP is working as designed. Your single prepend on one prefix with TWTC causes a slight preference for LVL3. Add another prepend if you want to further balance your ingress load away from TWTC.

Re: BGP multihoming with two address spaces

2014-01-29 Thread Jakob Heitz
It is likely that level3 is aggregating your route, but tw can't. Longest match wins. -- Jakob Heitz. > Date: Wed, 29 Jan 2014 03:32:17 -0800 > From: Joseph Jenkins > > I am seeking some feedback/help with my BGP configuration. I am peering with > two providers level3 and tw. Unfortunately

Re: BGP multihoming with two address spaces

2014-01-29 Thread Faisal Imtiaz
day, January 29, 2014 9:20:32 AM > Subject: RE: BGP multihoming with two address spaces > > Perhaps L3 is preferring the routes it hears from TW over the ones it hears > from you. Perhaps there is a community string you can attach to your > announcements to one or both providers

RE: BGP multihoming with two address spaces

2014-01-29 Thread Adam Greene
Jenkins [mailto:j...@breathe-underwater.com] Sent: Wednesday, January 29, 2014 7:45 AM Cc: nanog@nanog.org Subject: Re: BGP multihoming with two address spaces I am announcing two separate /24s. 8.37.93.0 and 207.114.212.0. Joe On Jan 29, 2014, at 4:21 AM, Sasa Ristic wrote: > How are

Re: BGP multihoming with two address spaces

2014-01-29 Thread Joseph Jenkins
I am announcing two separate /24s. 8.37.93.0 and 207.114.212.0. Joe On Jan 29, 2014, at 4:21 AM, Sasa Ristic wrote: > How are you announcing your address space now? > > On Wed, Jan 29, 2014 at 12:32 PM, Joseph Jenkins > wrote: >> I am seeking some feedback/help with my BGP configuration. I

Re: BGP multihoming with two address spaces

2014-01-29 Thread Sasa Ristic
How are you announcing your address space now? On Wed, Jan 29, 2014 at 12:32 PM, Joseph Jenkins wrote: > I am seeking some feedback/help with my BGP configuration. I am peering with > two providers level3 and tw. Unfortunately all of my address spaces are > preferring the route over tw rather

BGP multihoming with two address spaces

2014-01-29 Thread Joseph Jenkins
I am seeking some feedback/help with my BGP configuration. I am peering with two providers level3 and tw. Unfortunately all of my address spaces are preferring the route over tw rather than level3. I have tried Prepending my AS and the carriers AS to the path on the tw side and I see those up