Re: what's makes a route not valid in openbgpd?
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 [EMAIL PROTECTED] cat /etc/bgpd.conf | grep nexthop nexthop qualify via bgp [EMAIL PROTECTED] bgpctl reload reload request sent. request processed [EMAIL PROTECTED] bgpctl nei 38.104.XXX.37 refresh request processed [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 [EMAIL PROTECTED] thanks, aaron.glenn
Re: what's makes a route not valid in openbgpd?
* 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
Re: what's makes a route not valid in openbgpd?
On Mon, Oct 29, 2007 at 01:40:07PM -0700, Aaron Glenn wrote:
running 4.2/i386 as of two weeks ago, I've got a default route that
isn't being seen as valid and consequently not installed in the RIB.
when I first rolled this router out, however, it was valid and being
installed. while I'm interested in what could have happened between
then and now, I'm more interested in how the RDE actually makes its
decisions on validity. I see no obvious reason for this route to be
not valid.
everything else (demotion, 'prefix lists', etc) works great, however (-:
relevant info:
[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.65.50 100 0 174 i
I am learning that nexthop from another session with 174:
[EMAIL PROTECTED] bgpctl show fib bgp
flags: * = valid, B = BGP, C = Connected, S = Static
N = BGP Nexthop reachable via this route
r = reject route, b = blackhole route
flags destination gateway
*B38.103.65.50/32 38.104.XXX.37
[EMAIL PROTECTED] cat /etc/bgpd.conf
AS 10XX0
router-id 72.37.XXX.178
network inet connected
network inet static
network 38.98.XXX.0/24
neighbor 72.37.XXX.177 {
remote-as 10XX0
announce all
}
group COGENT {
remote-as 174
depend on bge1
softreconfig in yes
softreconfig out yes
neighbor 38.104.XXX.37 {
local-address 38.104.XXX.38
set prepend-self 3
announce self
}
neighbor 38.103.XXX.50 {
announce none
multihop 8
}
}
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.
--
:wq Claudio
Re: what's makes a route not valid in openbgpd?
On Mon, Oct 29, 2007 at 03:32:59PM -0700, Aaron Glenn wrote: 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 [EMAIL PROTECTED] cat /etc/bgpd.conf | grep nexthop nexthop qualify via bgp [EMAIL PROTECTED] bgpctl reload reload request sent. request processed [EMAIL PROTECTED] bgpctl nei 38.104.XXX.37 refresh request processed [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 [EMAIL PROTECTED] please restart your bgpd process it could be that the nexthop qualify options are not correctly reloaded on config change. Maybe a bgpctl nei 38.104.XXX.37 clear would work as well but I'm not 100% sure about that. Also include the bgpctl show nexthop and bgpctl show fib nexthop output. -- :wq Claudio
