On 2/22/18 10:20 AM, David Ahern wrote:
>> This breaks my scripts:
>> # ip -4 rule show
>> 0: from all lookup local
>> 32766: from all lookup main
>> 32767: from all lookup default
>>
>> # ip -4 rule del pref 0
>> RTNETLINK answers: No such file or directory
>>
>> Using iproute 4.15 in Fedor
On 2/22/18 1:23 AM, Ido Schimmel wrote:
>> diff --git a/net/core/fib_rules.c b/net/core/fib_rules.c
>> index 98e1066c3d55..c1d4ab5b2d9f 100644
>> --- a/net/core/fib_rules.c
>> +++ b/net/core/fib_rules.c
>> @@ -51,6 +51,7 @@ int fib_default_rule_add(struct fib_rules_ops *ops,
>> r->pref = pref;
Hi Donald,
On Tue, Feb 20, 2018 at 08:55:58AM -0500, Donald Sharp wrote:
> Allow a rule that is being added/deleted/modified or
> dumped to contain the originating protocol's id.
>
> The protocol is handled just like a routes originating
> protocol is. This is especially useful because there
> i
From: Donald Sharp
Date: Tue, 20 Feb 2018 08:55:58 -0500
> Allow a rule that is being added/deleted/modified or
> dumped to contain the originating protocol's id.
>
> The protocol is handled just like a routes originating
> protocol is. This is especially useful because there
> is starting to b
Allow a rule that is being added/deleted/modified or
dumped to contain the originating protocol's id.
The protocol is handled just like a routes originating
protocol is. This is especially useful because there
is starting to be a plethora of different user space
programs adding rules.
Allow the
