BGPd *CN Flags not showing

2008-09-25 Thread Insan Praja SW

Hi Misc,
Got this interfaces on my router,
$ ifconfig em
em0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500
lladdr 00:15:17:49:04:0d
description: ON_PORT_28
media: Ethernet autoselect (100baseTX full-duplex)
status: active
inet6 fe80::215:17ff:fe49:40d%em0 prefixlen 64 scopeid 0x1
em1: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1600
lladdr 00:07:e9:0f:44:e3
description: ON_PORT_30
media: Ethernet autoselect (1000baseT full-duplex,rxpause)
status: active
inet 202.149.67.123 netmask 0xfff8 broadcast 202.149.67.127
inet6 fe80::207:e9ff:fe0f:44e3%em1 prefixlen 64 scopeid 0x3
em2: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500
lladdr 00:15:17:49:04:0e
description: BACK_IF.ISAT.BDG
media: Ethernet autoselect (100baseTX full-duplex)
status: active
inet6 fe80::215:17ff:fe49:40e%em2 prefixlen 64 scopeid 0x4
inet 202.90.194.14 netmask 0xfffc broadcast 202.90.194.15   
 look at this



But BGPd said,

$ 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/30202.90.194.3
*BN   121.52.128.136/30202.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/29link#3
*SN   202.149.94.234/32202.149.67.121
*BN   202.149.95.0/24  202.149.67.121
*BN   202.149.95.172/30202.90.194.5
*BN   202.149.95.220/30202.90.194.5

No flags *CN on network 202.90.194.12/30.
Anyone can help?
Thanks,
Insan,



--
insandotpraja(at)gmaildotcom



Re: BGPd *CN Flags not showing

2008-09-25 Thread Claudio Jeker
On Thu, Sep 25, 2008 at 03:24:25PM +0700, Insan Praja SW wrote:
 Hi Misc,
 Got this interfaces on my router,
 $ ifconfig em
 em0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500
 lladdr 00:15:17:49:04:0d
 description: ON_PORT_28
 media: Ethernet autoselect (100baseTX full-duplex)
 status: active
 inet6 fe80::215:17ff:fe49:40d%em0 prefixlen 64 scopeid 0x1
 em1: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1600
 lladdr 00:07:e9:0f:44:e3
 description: ON_PORT_30
 media: Ethernet autoselect (1000baseT full-duplex,rxpause)
 status: active
 inet 202.149.67.123 netmask 0xfff8 broadcast 202.149.67.127
 inet6 fe80::207:e9ff:fe0f:44e3%em1 prefixlen 64 scopeid 0x3
 em2: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500
 lladdr 00:15:17:49:04:0e
 description: BACK_IF.ISAT.BDG
 media: Ethernet autoselect (100baseTX full-duplex)
 status: active
 inet6 fe80::215:17ff:fe49:40e%em2 prefixlen 64 scopeid 0x4
 inet 202.90.194.14 netmask 0xfffc broadcast 202.90.194.15   
  look at this


 But BGPd said,

 $ 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/30202.90.194.3
 *BN   121.52.128.136/30202.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/29link#3
 *SN   202.149.94.234/32202.149.67.121
 *BN   202.149.95.0/24  202.149.67.121
 *BN   202.149.95.172/30202.90.194.5
 *BN   202.149.95.220/30202.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.

-- 
:wq Claudio



Re: BGPd *CN Flags not showing

2008-09-25 Thread Henning Brauer
* 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/30202.90.194.3
  *BN   121.52.128.136/30202.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/29link#3
  *SN   202.149.94.234/32202.149.67.121
  *BN   202.149.95.0/24  202.149.67.121
  *BN   202.149.95.172/30202.90.194.5
  *BN   202.149.95.220/30202.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



Re: BGPd *CN Flags not showing

2008-09-25 Thread Insan Praja SW
On Thu, 25 Sep 2008 19:07:54 +0700, Henning Brauer [EMAIL PROTECTED]  
wrote:



* 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/30202.90.194.3
 *BN   121.52.128.136/30202.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/29link#3
 *SN   202.149.94.234/32202.149.67.121
 *BN   202.149.95.0/24  202.149.67.121
 *BN   202.149.95.172/30202.90.194.5
 *BN   202.149.95.220/30202.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'.



Hi Henning, Claudio and Misc@,
I have these;

$ bgpctl sh rib |more

flags: * = Valid,  = Selected, I = via IBGP, A = Announced
origin: i = IGP, e = EGP, ? = Incomplete

flags destination gateway  lpref   med aspath origin
*3.0.0.0/8   202.149.94.234 500 0 17826 4788 9304 80 i
I*3.0.0.0/8   202.90.194.13  100 0 17826 4788 9304 80 i

and on bgpd.conf;

jktcore =202.90.194.13

neighbor $jktcore {
remote-as   38776
announceall
announcecapabilities yes
softreconfigin yes
softreconfigout yes
descr   JKT-CORE01
route-reflector
set {localpref 100 nexthop 202.90.194.13}
}

on the filter;

allow from $jktcore inet prefixlen 8 - 30 set nexthop 202.90.194.13


and,

$ bgpctl sh next
Nexthop  State
202.149.95.221   valid
202.149.95.173   valid
121.52.128.137   valid
121.52.128.113   valid
202.90.194.110   valid
202.90.194.103   valid
202.90.194.102   valid
202.90.194.100   valid
202.149.95.45valid
202.90.194.17valid
202.90.194.14valid
202.90.194.13valid
202.90.194.9 valid
202.90.194.5 valid vlan6   UP, Ethernet, active, 100 MBit/s
202.90.194.4 valid vlan6   UP, Ethernet, active, 100 MBit/s
202.90.194.3 valid vlan6   UP, Ethernet, active, 100 MBit/s
202.90.194.2 valid vlan6   UP, Ethernet, active, 100 MBit/s
202.149.94.234   valid em1 UP, Ethernet, active, 1000 MBit/s

and,

Interface  Nexthop state  Flags  Link state
pflog0 ok UP unknown
vlan6  ok UP Ethernet, active, 100 MBit/s
vlan111ok UP Ethernet, active, 100 MBit/s
lo0ok UP unknown
enc0   invalid   unknown
em2ok UP Ethernet, active, 100 MBit/s
em1ok UP Ethernet, active, 1000 MBit/s
sk0ok UP Ethernet, active, 100 MBit/s
em0ok UP Ethernet, active, 100 MBit/s

$ ifconfig em2
em2: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500
lladdr 00:15:17:49:04:0e
description: BACK_IF.ISAT.BDG
media: Ethernet autoselect (100baseTX full-duplex)
status: active
inet6 fe80::215:17ff:fe49:40e%em2 prefixlen 64 scopeid 0x4
inet 202.90.194.14 netmask 0xfffc broadcast 202.90.194.15


Last boot dmesg, taken from /var/run/dmesg.boot

OpenBSD 4.4-current (GENERIC) #38: Sun Sep 14 13:34:34 WIT 2008
[EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC
RTC BIOS diagnostic error ffixed_disk,invalid_time
cpu0: Intel(R) Pentium(R) D CPU 3.00GHz (GenuineIntel 686-class) 3.01 GHz
cpu0:  
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,S

SE3,MWAIT,DS-CPL,EST,CNXT-ID,CX16,xTPR
real mem  = 1069604864 (1020MB)
avail mem = 1025802240 (978MB)
RTC BIOS diagnostic error ffixed_disk,invalid_time
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 09/13/07, SMBIOS rev. 2.4 @  
0x3fbe4000 (42 entries)
bios0: vendor Intel Corporation version  
S3000.86B.02.00.0048.042920081306 date 04/29/2008

bios0: Intel S3000AH
acpi0 at bios0: rev 0
acpi0: tables DSDT SLIC FACP APIC WDDT MCFG ASF! SSDT SSDT SSDT SSDT SSDT  
HEST BERT ERST EINJ
acpi0: wakeup devices SLPB(S4) P32_(S4) UAR1(S1) PEX4(S4) PEX5(S4)  
UHC1(S1) UHC2(S1) UHC3(S1) UHC4(S1) EHCI(S1) AC9M(S4) AZAL(

S4)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 4