On 4/9/19 10:31 PM, Govindarajulu Varadarajan wrote:
> However this worked
>
> @@ -1096,7 +1096,7 @@ static int fib_check_nh(struct fib_config *cfg,
> struct fib_nh *nh,
> u32 table = cfg->fc_table;
> int err;
>
> - if (nh->fib_nh_gw_family == AF_INET)
> + if (nh->fib_
On Tue, Apr 9, 2019 at 7:13 PM David Ahern wrote:
>
> On 4/9/19 5:08 PM, Govindarajulu Varadarajan wrote:
> > On Fri, Apr 5, 2019 at 4:32 PM David Ahern wrote:
> >>
> >> From: David Ahern
> >>
> >> fib_check_nh is currently huge covering multiple uses cases - device only,
> >> device + gateway,
On 4/9/19 5:08 PM, Govindarajulu Varadarajan wrote:
> On Fri, Apr 5, 2019 at 4:32 PM David Ahern wrote:
>>
>> From: David Ahern
>>
>> fib_check_nh is currently huge covering multiple uses cases - device only,
>> device + gateway, and device + gateway with ONLINK. The next patch adds
>> validation
On 4/9/19 5:08 PM, Govindarajulu Varadarajan wrote:
> On Fri, Apr 5, 2019 at 4:32 PM David Ahern wrote:
>>
>> From: David Ahern
>>
>> fib_check_nh is currently huge covering multiple uses cases - device only,
>> device + gateway, and device + gateway with ONLINK. The next patch adds
>> validation
On Fri, Apr 5, 2019 at 4:32 PM David Ahern wrote:
>
> From: David Ahern
>
> fib_check_nh is currently huge covering multiple uses cases - device only,
> device + gateway, and device + gateway with ONLINK. The next patch adds
> validation checks for IPv6 which only further complicates it. So, brea
From: David Ahern
fib_check_nh is currently huge covering multiple uses cases - device only,
device + gateway, and device + gateway with ONLINK. The next patch adds
validation checks for IPv6 which only further complicates it. So, break
fib_check_nh into 2 helpers - one for gateway validation and
