* Claudio Jeker <[EMAIL PROTECTED]> [2008-09-25 11:15]: > > $ bgpctl sh fib next > > flags: * = valid, B = BGP, C = Connected, S = Static > > N = BGP Nexthop reachable via this route > > r = reject route, b = blackhole route > > > > flags destination gateway > > *BN 121.52.128.0/24 202.149.67.121 > > *BN 121.52.128.112/30 202.90.194.3 > > *BN 121.52.128.136/30 202.90.194.5 > > *CN 202.90.194.0/29 link#8 > > *BN 202.90.194.8/30 202.90.194.5 > > *BN 202.90.194.16/30 202.90.194.3 > > *BN 202.90.194.96/27 202.90.194.5 > > *CN 202.149.67.120/29 link#3 > > *SN 202.149.94.234/32 202.149.67.121 > > *BN 202.149.95.0/24 202.149.67.121 > > *BN 202.149.95.172/30 202.90.194.5 > > *BN 202.149.95.220/30 202.90.194.5 > > > > No flags *CN on network 202.90.194.12/30. > > Anyone can help? > > Did you configure the interface after starting bgpd? > If this is the case I think I know where the problem is.
no, he simply doesn't have a route with nexthop within 202.90.194.12/30, thus it does not show up in 'show nexthop'. -- 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
