Hi Max,
There was indeed a problem with the netmask, so BIRD did not consider the
peer as directly connected.
thanks for your help.
Julien
2018-04-25 23:33 GMT+02:00 Maximilian Wilhelm :
> Anno domini 2018 Julien Sansonnens scripsit:
>
> Hi,
>
> > I'm having a hard time trying to peer with some
Hi,
Thanks. I notice this codes in rte_better() in file rt-table.c. Since iBGP
and eBGP have same protocol preference, that mean route preference are also
same. In this case, if we have one iBGP instance and one eBGP instance, since
instance address are different, route selection will entr
Cool Tim,
right!, just works as expected that way.
Thanks.
Jorge.
> El 26 abr 2018, a las 15:44, Tim Weippert escribió:
>
> Hi Jorge,
>
> i had not exactly your config, but i get used of many checks on extended
> community like:
>
> if ( bgp_ext_community ~ [ (rt, MYAS, 6200..6299)
Hi Jorge,
i had not exactly your config, but i get used of many checks on extended
community like:
if ( bgp_ext_community ~ [ (rt, MYAS, 6200..6299) ] ) then {
;
}
and they work as expected. So i would think on standard communities it
should work like:
if ( bgp_community ~ [ (65000
Hi there,
just wondering how to migrate to Bird configuration this entry from another
RR:
“regex 65000:50[0-9][0-9]”
applied to a BGP import route-map on community match.
Tried on Bird:
“if ([(65000,5000..5099)]) ~ bgp_community then “action"
After that, no prefixes h
