* Aaron Glenn <[EMAIL PROTECTED]> [2007-10-29 23:33]: > On 10/29/07, Claudio Jeker <[EMAIL PROTECTED]> wrote: > > > > The nexthop depends on a bgp route which is considered evil and therefor > > not allowed by default. Add "nexthop qualify via bgp" to the global config > > part and your setup should work again. > > Henning hit me with that clue-by-four privately, and that does make > perfect sense...but it's still not working. Below is with a refresh, > tried it with a hard clear as well. I have "nexthop quality via bgp" > properly situation in the global configuration area. > > At the risk of being hit by the clue-by-four again...here goes nothing: > > [EMAIL PROTECTED] bgpctl show rib nei 38.103.65.50 in > flags: * = Valid, > = Selected, I = via IBGP, A = Announced > origin: i = IGP, e = EGP, ? = Incomplete > > flags destination gateway lpref med aspath origin > 0.0.0.0/0 38.103.XXX.50 100 0 174 i
why do you XXX the 65? :) wnat does "bgpctl sh nex" have to say about it? and "bgpctl sh fi 38.103.65.50"? -- Henning Brauer, [EMAIL PROTECTED], [EMAIL PROTECTED] BS Web Services, http://bsws.de Full-Service ISP - Secure Hosting, Mail and DNS Services Dedicated Servers, Rootservers, Application Hosting - Hamburg & Amsterdam
