Rare project developers

[mc36 <>]

-------- Forwarded Message --------
Subject: Re: Bgp with polka
Date: Wed, 2 Feb 2022 02:03:58 +0100
From: mc36 <>
Reply-To: 
To: Everson Borges <>

hi,
you're welcome! i was thinking about it further and i had an idea: so if 
you're using bgp,
and bgp have a lot of possibilities to tag a given prefix... mostly they use 
community
values on origination to mark by a given prefix, let's say to be polka routed 
to tunnel1...
so i've just added two additional more filtering capability to the autoroute 
candidates:
https://github.com/mc36/freeRouter/commit/253744a60516476e9b93a6ef0351e0babaef5526
so from now, you can use the cisco xe route-map convention,
or even better, the cisco xr route-policy matching language
to steer a specific set of prefixes to the tunnel...
regards,
cs




sid(cfg-if)#show config-differences
route-map asdf
 sequence 10 action permit
 sequence 10 match network 10.4.0.0/17 ge 17 le 32
 exit
route-policy qwer
 sequence 10 if network 10.4.128.0/17 ge 17 le 32
 sequence 20   pass
 sequence 30 enif
 exit
interface tunnel1
 no description
 tunnel vrf v1
 tunnel source loopback0
 tunnel destination 10.10.10.4
 tunnel domain-name 10.10.10.2
 tunnel mode srmpls
 vrf forwarding v1
 ipv4 address 5.5.5.5 255.255.255.252
 ipv4 autoroute bgp4 65535 10.4.255.0 5.5.5.6 recursive
 no shutdown
 no log-link-change
 exit

sid(cfg-if)#$65535 10.4.255.0 5.5.5.6 recursive include-map asdf
sid(cfg-if)#show ipv4 just-interface v1 tunnel1
typ  prefix        metric  iface    hop      time
C    5.5.5.4/30    0/0     tunnel1  null     00:01:18
LOC  5.5.5.5/32    0/1     tunnel1  null     00:01:18
B    10.4.2.0/24   200/0   tunnel1  5.5.5.6  00:01:24
B    10.4.3.0/24   200/0   tunnel1  5.5.5.6  00:01:24
B    10.4.4.0/30   200/0   tunnel1  5.5.5.6  00:01:24
B    10.4.4.40/30  200/0   tunnel1  5.5.5.6  00:01:24
B    10.4.5.0/24   200/0   tunnel1  5.5.5.6  00:01:24
B    10.4.6.0/24   200/0   tunnel1  5.5.5.6  00:01:24
B    10.4.7.0/24   200/0   tunnel1  5.5.5.6  00:01:24
B    10.4.8.0/24   200/0   tunnel1  5.5.5.6  00:01:24

sid(cfg-if)#$65535 10.4.255.0 5.5.5.6 recursive include-policy qwer
sid(cfg-if)#show ipv4 just-interface v1 tunnel1
typ  prefix         metric  iface    hop      time
C    5.5.5.4/30     0/0     tunnel1  null     00:01:31
LOC  5.5.5.5/32     0/1     tunnel1  null     00:01:31
B    10.4.128.0/24  200/0   tunnel1  5.5.5.6  00:01:37
B    10.4.255.0/24  200/0   tunnel1  5.5.5.6  00:01:37

sid(cfg-if)#



On 2/1/22 17:26, Everson Borges wrote:
> Thanks
>
> I will test.
>
> Em ter., 1 de fev. de 2022   s 12:46, mc36 < <>> 
> escreveu:
>
>     hi,
>     here with this change
>     
> https://github.com/mc36/freeRouter/commit/181c17f303818a7c3729876ed96adb2abd2553a1 
> <https://github.com/mc36/freeRouter/commit/181c17f303818a7c3729876ed96adb2abd2553a1>
>     from now you can explicitly specify which prefixes (not) to autoroute...
>     regards,
>     cs
>
>     sid(cfg-if)#show config-differences
>     prefix-list asdf
>         sequence 10 permit 10.4.128.0/17 <http://10.4.128.0/17> ge 17 le 32
>         exit
>     interface tunnel1
>         no description
>         tunnel vrf v1
>         tunnel source loopback0
>         tunnel destination 10.10.10.4
>         tunnel domain-name 10.10.10.1
>         tunnel mode srmpls
>         vrf forwarding v1
>         ipv4 address 5.5.5.5 255.255.255.252
>         ipv4 autoroute bgp4 65535 10.4.255.0 5.5.5.6 recursive include-list 
> asdf
>         no shutdown
>         no log-link-change
>         exit
>
>     sid(cfg-if)#show ipv4 just-interface v1 tunnel1
>     typ   prefix              metric   iface      hop         time
>     C 5.5.5.4/30 <http://5.5.5.4/30>        0/0        tunnel1   null        
> 00:00:28
>     LOC 5.5.5.5/32 <http://5.5.5.5/32>        0/1        tunnel1   null       
>  00:00:28
>     B 10.4.128.0/24 <http://10.4.128.0/24>   200/0     tunnel1   5.5.5.6   
> 00:00:29
>     B 10.4.255.0/24 <http://10.4.255.0/24>   200/0     tunnel1   5.5.5.6   
> 00:00:29
>
>     sid(cfg-if)#ipv4 autoroute bgp4 65535 10.4.255.0 5.5.5.6 recursive
>     sid(cfg-if)#show ipv4 just-interface v1 tunnel1
>     typ   prefix              metric   iface      hop         time
>     C 5.5.5.4/30 <http://5.5.5.4/30>        0/0        tunnel1   null        
> 00:00:37
>     LOC 5.5.5.5/32 <http://5.5.5.5/32>        0/1        tunnel1   null       
>  00:00:37
>     B 10.4.2.0/24 <http://10.4.2.0/24>      200/0     tunnel1   5.5.5.6   
> 00:00:38
>     B 10.4.3.0/24 <http://10.4.3.0/24>      200/0     tunnel1   5.5.5.6   
> 00:00:38
>     B 10.4.4.0/30 <http://10.4.4.0/30>      200/0     tunnel1   5.5.5.6   
> 00:00:38
>     B 10.4.4.40/30 <http://10.4.4.40/30>     200/0     tunnel1   5.5.5.6   
> 00:00:38
>     B 10.4.5.0/24 <http://10.4.5.0/24>      200/0     tunnel1   5.5.5.6   
> 00:00:38
>     B 10.4.6.0/24 <http://10.4.6.0/24>      200/0     tunnel1   5.5.5.6   
> 00:00:38
>     B 10.4.7.0/24 <http://10.4.7.0/24>      200/0     tunnel1   5.5.5.6   
> 00:00:38
>     B 10.4.8.0/24 <http://10.4.8.0/24>      200/0     tunnel1   5.5.5.6   
> 00:00:38
>     B 10.4.128.0/24 <http://10.4.128.0/24>   200/0     tunnel1   5.5.5.6   
> 00:00:38
>     B 10.4.255.0/24 <http://10.4.255.0/24>   200/0     tunnel1   5.5.5.6   
> 00:00:38
>     B 10.18.1.12/30 <http://10.18.1.12/30>   200/0     tunnel1   5.5.5.6   
> 00:00:38
>
>     sid(cfg-if)#
>
>
>     On 2/1/22 15:37, mc36 wrote:
>      > i'll introduce a knob soon to be able to filter with a list...
>      > (then you have to exclude the core loopbacks with that knob...)
>
>
>
> --
> Att.
> Everson Scherrer Borges