Rare project developers

[mc36 <>]

and fun fact, imho i'll be able to do the same for the vpls and the evpn afis 
:))))

On 3/3/23 12:01, mc36 wrote:
> hi, guys,
>
> imho from now, freerouter have cheat-less colorful resolution for vpnv4/vpnv6 
> afis:
>
> https://github.com/rare-freertr/freeRtr/commit/335d83792d7123ca164691f124ceab71a98e21b9
>
> unfortunately this contains a smaller refactoring also, i just forgot to 
> commit that beforehand... :)
>
>
> the code is still not covered by a test case, that will be the next,
>
> then i'll get back to you with a new topology for the plugfest...
>
> happy weekend,
> thanks,
> cs
>
> sid#show config-differences
> router bgp4 65535 vrf v1
>    afi-vrf niif set-vrf v2 ipv4
>    exit
>
> sid#clear ipv4 bgp 65535 all in vpnuni
> sid#show ipv4 route niif | first 10
> typ   prefix                           metric         iface           hop     
>               time
> B       0.0.0.0/0                     200/0           null@v2:4   10.10.10.25 
>   00:00:02
> B       4.0.0.0/9                     200/0           null@v2:4   10.10.10.25 
>   00:00:02
> B       4.23.88.0/24               200/0           null@v2:4   10.10.10.25   
> 00:00:02
> B       4.23.89.0/24               200/0           null@v2:4   10.10.10.25   
> 00:00:02
> B       4.23.92.0/23               200/0           null@v2:4   10.10.10.25   
> 00:00:02
> B       4.23.94.0/23               200/0           null@v2:4   10.10.10.25   
> 00:00:02
> B       4.35.69.0/24               200/0           null@v2:4   10.10.10.25   
> 00:00:02
> B       4.38.0.0/21                 200/0           null@v2:4   10.10.10.25   
> 00:00:02
> B       4.38.8.0/21                 200/0           null@v2:4   10.10.10.25   
> 00:00:02
>
> sid#configure revert
>           1: router bgp4 65535 vrf v1
>           2:   no afi-vrf niif set-vrf v2 ipv4
>           3:   exit
>
> errors=0
>
> router bgp4 65535 vrf v1
>    afi-vrf niif set-vrf v2 ipv4
>    exit
>
> sid#clear ipv4 bgp 65535 all in vpnuni
> sid#show ipv4 route niif | first 10
> typ   prefix                           metric           iface           hop   
>                 time
> B       0.0.0.0/0                     200/0             null@v1:4   
> 10.10.10.25   00:00:02
> B       4.0.0.0/9                     200/0             null@v1:4   
> 10.10.10.25   00:00:02
> B       4.23.88.0/24               200/0             null@v1:4   10.10.10.25  
>  00:00:02
> B       4.23.89.0/24               200/0             null@v1:4   10.10.10.25  
>  00:00:02
> B       4.23.92.0/23               200/0             null@v1:4   10.10.10.25  
>  00:00:02
> B       4.23.94.0/23               200/0             null@v1:4   10.10.10.25  
>  00:00:02
> B       4.35.69.0/24               200/0             null@v1:4   10.10.10.25  
>  00:00:02
> B       4.38.0.0/21                 200/0             null@v1:4   10.10.10.25 
>   00:00:02
> B       4.38.8.0/21                 200/0             null@v1:4   10.10.10.25 
>   00:00:02
>
> sid#
>
>
>
> On 2/28/23 23:21, mc36 wrote:
> > hi,
> >
> > On 2/28/23 22:39, Kaliraj Vairavakkalai wrote:
> > > That     s cool. So now we have two demo setups:
> > >
> > > 1/ Csaba     s setup with FreeRTR as Ingress-PE doing colorful resolution.
> > >
> > > 2/ Natz setup with FreeRTR as ASBR doing colorful resolution.
> > >
> > > We could have a combo of the two setups, to show FreeRTR in both ASBR and 
> > > ingress-PE roles.     ;)
> >
> > well, for a really really proper color resolution imho i need to introduce the 
> > "afi-vrf cust-blue resolve-in core-blue" knob...
> > it'll simply set the route's underlaying table like when we need to send out 
> > a vrf packet in mpls in the core vrf, but here,
> > it'll a per vrf override that i'll set that paramter to a user defined 
> > table... no fallback yet, just a static mechanism...
> > that'll be the first tomorrow what i'll start playing with... :)
> >
> >
> > > Just some comments -
> > >
> > > It     s worth noting that:
> > >
> > >          route-policy ibgp-in
> > >
> > >              sequence 10 if extcomm 2562:0:100
> > >
> > >              sequence 20         set vrf v2 ipv4
> > >
> > >              sequence 30         pass
> > >
> > >              sequence 40 enif
> > >
> > >              sequence 50 if extcomm 2562:0:200
> > >
> > >              sequence 60         set vrf v3 ipv4
> > >
> > >              sequence 70         pass
> > >
> > >              sequence 80 enif
> > >
> > >              sequence 90 drop
> > >
> > >              exit
> > >
> > > This policy config kind of implements the       resolution-scheme     . :)
> >
> > yeahh, i knew that matching against the rd is not the color but the path... :)
> >
> >
> >
> > > It works with LDP tunnels in VRFs v2, v3. BGP-CT routes are able to resolve 
> > > over LDP routes
> > >
> > > (in main VRF v1 or color VRFs v2,v3), and create SWAP routes properly.
> > >
> > > We could not make BGP routes resolve over RSVP-TE Tunnel routes in any VRF. 
> > > That     s why we used
> > >
> > > LDP-tunnels in previous IETF demo as-well. We may be missing something there.
> >
> > so that was just another dirty hack that i put the rsvp to a dummy vrf to 
> > have a color on it.... :)
> >
> >
> > > And, the code-change in rtrBgpNeigh.java was needed to make the following 
> > > config work:
> >
> > [..]
> >
> > let's discuss this on my previous mail, i did a lot of changes to that part 
> > as i realized
> > that you were right and a lot were missing on that part of the code.... :)
> > thanks again for spotting it... :)
> >
> > thanks,
> > cs