Thanks, will have a look at it again.

On 21 May 2012, at 9:58 PM, Claudio Jeker wrote:

> On Mon, May 21, 2012 at 02:58:50PM +0200, Hendrik Meyburgh wrote:
>> Hi,
>>
>> I have a problem where the default install of 5.1 does not import routes
into
>> the rdomain solely based on the community but it uses the route
>> distinguisher.
>>
>> This causes the below scenario:
>>
>> in bgpd.conf
>> rdomain 2 {
>>        descr "Testing"
>>        rd 65001:238
>>        import-target rt 65001:238
>>        export-target rt 65001:238
>>        depend on mpe2
>>        network 192.168.10.2/32
>> }
>>
>>
>> from bgpctl show ip bgp detail:
>>
>> Route that gets imported:
>> BGP routing table entry for rd 65001:238 192.168.76.128/25
>>    65001
>>    Nexthop 172.16.0.1 (via 10.10.10.4) from AS 65002 peer 1 (172.16.0.1)
>>    Origin incomplete, metric 0, localpref 100, external, valid, best
>>    Last update: 00:14:46 ago
>>    Ext. communities: rt 65001:238
>>
>> route that does not get imported:
>> BGP routing table entry for rd 172.16.0.1:425 192.168.70.0/23
>>    65001 64544
>>    Nexthop 172.16.0.1 (via 10.10.10.4) from AS 65002 peer 1 (172.16.0.1)
>>    Origin IGP, metric 0, localpref 100, external, valid, best
>>    Last update: 00:14:46 ago
>>    Ext. communities: rt 65001:238
>>
>>
>> I came across the below link which contained some suggested patches where
some
>> has been imported into -current and some have not.
>>
>>
http://www.mentby.com/Group/openbsd-misc/route-target-import-export-in-bgpd.h
>> tml
>>
>> My question is, how do I know into what source these patches must be merged
as
>> I have tried -current and -stable but on both I ran into issues merging as
>> there as some problems with the spacing when copying from the browsers.
>
> Yeah, you need to fetch the raw message for that. IIRC marc.info offers
> that. Copy-paste almost never works.
>
>> Do anyone know if this fix has been implemented already into a tree that I
am
>> not aware of?
>
> This is fixed in -current. At least the problem with using the RD for
> distribution. What is not yet fixed is the problem with reimporting a
> prefix on the same machine but into different routing domain. The problem
> here is that I don't like my own diff. I want a cleaner fix for this but
> did not have time to fix this.
>
> --
> :wq Claudio

Reply via email to