[130292] in North American Network Operators' Group
Re: BGP next-hop
daemon@ATHENA.MIT.EDU (Heath Jones)
Thu Sep 30 19:34:20 2010
In-Reply-To: <m239sqzzdk.wl%randy@psg.com>
Date: Fri, 1 Oct 2010 00:32:17 +0100
From: Heath Jones <hj1980@gmail.com>
To: Randy Bush <randy@psg.com>
Cc: North American Network Operators Group <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
> it seems it gets the bgp route for 147.28.0.0/16 and then can not
> resolve the next hop. =A0it would not recurse to the default exit.
>
> of course it was solved by
> =A0 =A0ip route 147.28.0.0 =A0255.255.0.0 =A042.666.77.11
> but i do not really understand in my heart why i needed to do this.
Neither do I, Randy.
I have seen recursive routing done - perhaps on a juniper - i really
cannot remember.
Given that the packet would be originating from the device itself (not
hardware forwarded), it would make sense that it should be able to
perform a recursive lookup. I'd put it down to an implementation
thing..
Unrelated, I was doing some thinking about a multihomed site and using
BGP advertisments sent out one link (provider 1) to influence the
sending of the advertisments out of the other link (provider 2). Long
story short I needed to know how long bgp nlri's take to traverse the
net, and subsequently have a paper that you co-authored open in
another tab - well done! :)
