[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAJieiUifEsTjycJ1vkuZaiz5j7jxe-H=wD75_eb9Vh+XPdakBQ@mail.gmail.com>
Date: Thu, 1 Mar 2018 15:08:19 -0800
From: Roopa Prabhu <roopa@...ulusnetworks.com>
To: Eric Dumazet <eric.dumazet@...il.com>
Cc: David Miller <davem@...emloft.net>, netdev@...r.kernel.org,
David Ahern <dsa@...ulusnetworks.com>,
Nikolay Aleksandrov <nikolay@...ulusnetworks.com>,
Ido Schimmel <idosch@...lanox.com>,
Paolo Abeni <pabeni@...hat.com>
Subject: Re: [PATCH net-next v2 1/5] net: fib_rules: support for match on
ip_proto, sport and dport
On Thu, Mar 1, 2018 at 2:48 PM, Eric Dumazet <eric.dumazet@...il.com> wrote:
> On Tue, 2018-02-27 at 19:52 -0800, Roopa Prabhu wrote:
>> From: Roopa Prabhu <roopa@...ulusnetworks.com>
>>
>> uapi for ip_proto, sport and dport range match
>> in fib rules.
>
>
> Hi Roopa
>
> FRA_UNSPEC,
>> FRA_DST, /* destination address */
>> @@ -59,6 +64,9 @@ enum {
>> FRA_L3MDEV, /* iif or oif is l3mdev goto its table */
>> FRA_UID_RANGE, /* UID range */
>> FRA_PROTOCOL, /* Originator of the rule */
>> + FRA_IP_PROTO, /* ip proto */
>> + FRA_SPORT_RANGE, /* sport */
>> + FRA_DPORT_RANGE, /* dport */
>> __FRA_MAX
>> };
>
>
> It seems you forgot to update FRA_GENERIC_POLICY ?
>
indeed. will submit a fix. thanks Eric!.
Powered by blists - more mailing lists