Re: OpenBGPD: Announce all problem and strange rib-out entries.

2008-12-28 Thread Pehr Söderman
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
 
And I managed to grab the bgpctl data with a slightly different
version of the bgpd config:

The line

network 192.168.0.0/16

was commented out when I grabbed the data, but it doesn't seem to
change the behaviour.

/Pehr Svderman
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
 
iEYEARECAAYFAklXfsUACgkQlIRLofxhDjbtRQCgrFUEIWXTVmk1DlpHW8MxeiKO
kRQAoJ2TAsciTPwgi7vW10/KijL01PwS
=Ce60
-END PGP SIGNATURE-



OpenBGPD: Announce all problem and strange rib-out entries.

2008-12-27 Thread Pehr Söderman
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
 
Hello!

I hope this is the right forum to discuss OpenBGP on OpenBSD.

I am setting up a lab network using a combination of OpenBSD 4.4
(About as standard install as they get) and Junier routers and have
run into an interesting problem with OpenBGP. To summarize the issue,
it acts as if "announce self" is turned on for all neighbours, even
when it's not. I also get a weird duplicate entry in the rib-out for
local nets, if the router gets a more specific route from a neighbour
for a local network. No filters are active. Nada. Zip. I am not
certain if this is a bug with OpenBGPD, the juniper-bgpd combination
or (perhaps most likely) a configuration error on my side.

Here is the bgpd.conf. (I have obfuscated some addresses and cut it
short to save space)

# sample bgpd configuration file
# see bgpd.conf(5)

# global configuration
AS 65000
router-id x.y.z.62
listen on x.y.z.62
fib-update yes

#network inet connected
network 192.168.0.0/16
network 10.0.0.0/8

# neighbors and peers
group "AS 65011 A1" {
remote-as 65011
neighbor x.y.z.34
announce all
}
group "AS 65012 A2" {
remote-as 65012
neighbor x.y.z.35
announce all
}
group "AS 65013 A3" {
remote-as 65013
neighbor x.y.z.36
announce all
}
group "AS 65014 A4" {
remote-as 65014
neighbor x.y.z.37
announce all
}
<16 more neighbors>

And some bgpctl outputs.

# bgpctl show summary
Neighbor AS   MsgRcvdMsgSentOutQ  Up/Down
State/PrfRcvd
<16 more neighbors>
x.y.z.3765014 59 43 0 00:25:15  0
x.y.z.3665013  0  0 0 NeverActive
x.y.z.3565012 91 59 0 00:39:01  2
x.y.z.3465011  0  0 0 NeverActive

# bgpctl show network
flags: S = Static
flags destination
* 10.0.0.0/8

# bgpctl show rib
flags: * = Valid, > = Selected, I = via IBGP, A = Announced
origin: i = IGP, e = EGP, ? = Incomplete

flags destination gateway  lpref   med aspath origin
AI*>  10.0.0.0/8  0.0.0.0100 0 i
*>10.2.0.0/16 x.y.z.35   100 0 65012 i
*>192.168.2.0/24  x.y.z.35   100 0 65012 i

# bgpctl show rib detail

BGP routing table entry for 10.0.0.0/8
Nexthop 0.0.0.0 (via 0.0.0.0) from LOCAL: ID x.y.z.62 (x.y.z.62)
Origin IGP, metric 0, localpref 100, internal, valid, best, announced
Last update: 00:03:58 ago

BGP routing table entry for 10.2.0.0/16
65012
Nexthop x.y.z.35 (via x.y.z.35) from x.y.z.35 (192.168.2.2)
Origin IGP, metric 0, localpref 100, external, valid, best
Last update: 00:55:38 ago
Aggregator: 62717.0 [192.168.2.2]

BGP routing table entry for 192.168.2.0/24
65012
Nexthop x.y.z.35 (via x.y.z.35) from x.y.z.35 (192.168.2.2)
Origin IGP, metric 0, localpref 100, external, valid, best
Last update: 00:55:38 ago
Aggregator: 62717.0 [192.168.2.2]

# bgpctl show rib out
flags: * = Valid, > = Selected, I = via IBGP, A = Announced
origin: i = IGP, e = EGP, ? = Incomplete

flags destination gateway  lpref   med aspath origin
AI*>  10.0.0.0/8  0.0.0.0100 0 i
AI*>  10.0.0.0/8  0.0.0.0100 0 i

#  bgpctl show rib out detail

BGP routing table entry for 10.0.0.0/8
Nexthop 0.0.0.0 (via 0.0.0.0) from LOCAL: ID x.y.z.62 (x.y.z.62)
Origin IGP, metric 0, localpref 100, internal, valid, best, announced
Last update: 00:01:02 ago

BGP routing table entry for 10.0.0.0/8
Nexthop 0.0.0.0 (via 0.0.0.0) from LOCAL: ID x.y.z.62 (x.y.z.62)
Origin IGP, metric 0, localpref 100, internal, valid, best, announced
Last update: 00:01:02 ago

.35 announces 2 networks: 10.2.0.0/16 and 192.168.2.0/24. I would have
expected .62 to reannounce both. The 10.2/16 and 192.168.2/24 routes
are correctly entered into the local routing table. However, for some
reason they are not announced, and never gets the announced flag.

Can somebody with more experience of BGPD help me solve this mystery?

/Pehr Svderman
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
 
iEYEARECAAYFAklWfoQACgkQlIRLofxhDjZJ4gCfUtH0RcaYXOanFTJMMGbN5/OE
r3EAoIJZoqi+FI+9Nt9DHle2WDDd3TkE
=bbe4
-END PGP SIGNATURE-