On Wed, Apr 04, 2012 at 10:37:20AM +0200, Rimi Philippe wrote:
> Hello,
> Any hints on how to troubleshoot this issue? I'm looking for some kind
> of debug to see what is going from rib to fib in order to understand
> why the prefixes are not imported.
>
Hmm. Looks like I go t confused by the old BGP MPLS VPN RFC where the RD
was somewhat strangly declared. In other words bgpd filters on the RD as
well. This is a bug and I will fix it ASAP.
--
:wq Claudio
> Thanks,
>
> Rimi
>
> Le 1 avril 2012 16:24, Rimi Philippe <m...@remiphilippe.fr> a icrit :
> > Hello,
> > I'm testing OpenBSD with L3VPN, everything is working fine except from
> > the RT import / export side.
> >
> > I usually configure my VPN with PE Loopback:identifier, so my config
> > looks like this:
> > PE1:
> > rdomain 20 {
> > rd 1.1.1.1:20
> > import-target rt 2.2.2.2:20
> > export-target rt 1.1.1.1:20
> > depend on mpe20
> > network inet connected
> > }
> >
> > PE2:
> > rdomain 20 {
> > rd 2.2.2.2:20
> > import-target rt 1.1.1.1:20
> > export-target rt 2.2.2.2:20
> > depend on mpe20
> > network inet connected
> > }
> >
> > This kind of configuration works on Cisco devices for example, but here
> >
> > PE1:
> >
> > # bgpctl show fib table 20
> > flags: * = valid, B = BGP, C = Connected, S = Static
> > N = BGP Nexthop reachable via this route
> > r = reject route, b = blackhole route
> >
> > flags prio destination gateway
> > *C 0 127.0.0.0/8 link#0
> > *C 4 172.16.35.0/24 link#2
> > *C 0 ::1/128 link#0
> >
> > PE2:
> >
> > # bgpctl sho fib table 20
> > flags: * = valid, B = BGP, C = Connected, S = Static
> > N = BGP Nexthop reachable via this route
> > r = reject route, b = blackhole route
> >
> > flags prio destination gateway
> > *C 0 127.0.0.0/8 link#0
> > *C 4 172.16.39.0/24 link#3
> > *C 0 ::1/128 link#0
> >
> > It works fine when I set the same RD on both PE, but that's not really
> > what I'm looking for.
> >
> > I can't find much debug information, any hints on how to tshoot this?
> >
> > Thanks for your help,
> >
> > Remi
