Hi Ondrej,
On 2020-12-02 17:48, Ondrej Zajicek wrote:
You can try this patch and set 'weight' during export to kernel
protocol.
Cool! Works as expected - and this actually opens many interesting
opportunities.
Thank you!
Regards,
Alexander.
On Fri, Nov 20, 2020 at 10:49:32AM +0100, Alexander Demenshin wrote:
>
> On 2020-11-19 22:25, Maria Matějka wrote:
>
> > Would it be feasible for you to have a special route attribute to be
> > set in filters that would control the nexthop weight?
>
> Sure, this is quite feasible, especially if
On 2020-11-19 22:25, Maria Matějka wrote:
Would it be feasible for you to have a special route attribute to be
set in filters that would control the nexthop weight?
Sure, this is quite feasible, especially if this attribute could be
applied
to any route (exported to kernel), i.e. regardles
On 11/19/20 9:25 PM, Maria Matějka wrote:
> Hello!
>
> Would it be feasible for you to have a special route attribute to be
> set in filters that would control the nexthop weight? That seems to be
> probably a most simple solution.
That would certainly work for me, one can then use any combinat
Hello!
Would it be feasible for you to have a special route attribute to be set in
filters that would control the nexthop weight? That seems to be probably a most
simple solution.
Maria
On November 19, 2020 5:42:38 PM GMT+01:00, Nigel Kukard
wrote:
>On 11/19/20 4:06 PM, Alexander Demenshin
Hi,
I have two uplinks (different AS), and one is more stable/preferred,
but when "merge paths" is set to on, all routes are generated with
weight 1:
5.21.41.0/24 proto bird
nexthop via 10.16.0.1 dev uplink1 weight 1
nexthop via 10.17.0.1 dev uplink2 weight 1
Is there any way
