On Fri, Sep 16, 2011 at 2:34 PM, Claudio Jeker <cje...@diehard.n-r-g.com>wrote:
> On Wed, Aug 31, 2011 at 04:37:49PM +0200, Tony Sarendal wrote: > > On Wed, Aug 31, 2011 at 4:24 PM, Josh Hoppes <josh.hop...@gmail.com> > wrote: > > > > > Why are you using "set nexthop self" and then trying to change that > > > with the filter "allow quick to 172.29.1.52 set nexthop 172.29.1.200". > > > If you don't want your nexthop to be yourself don't tell bgpd to do > > > that. > > > > > > > > To show a bug in bgpctl/bgpd (or where ever it may be). > > Dont you want to be able to trust the information bgpctl gives you ? > > > > Yes there is a bug in bgpd. The problem is that set nexthop self was > sticky and overriding the other set nexthop that came after. > > The following diff should solve those issues. > -- > :wq Claudio > Looks fine when I apply it to the test boxes. Cheers. /Tony
