lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Wed, 19 Aug 2015 12:38:11 +0200
From:	Andreas Schultz <>
To:	David Ahern <>,
Subject: Re: [net-next]: unable to add routes to tables

On 08/18/2015 07:26 PM, David Ahern wrote:
> On 8/18/15 10:57 AM, Andreas Schultz wrote:
>> Hi,
>> It seems that the policy for adding routes to tables has changed between
>> Linux 4.2-rc6 and net-next.
>> In Linux main line (tested up to 4.2-rc6), with this main routing table:
>> # ip route show table main
>> ...
>> dev vnf-xe1p0  proto kernel  scope link  src
>> and an empty table 100, this works:
>> # ip route add via table 100 dev vnf-xe1p0
>> With net-next at commit d52736e24fe2e927c26817256f8d1a3c8b5d51a0, the
>> same command leads to an:
>> # ip route add via table 100 dev vnf-xe1p0
>> RTNETLINK answers: Resource temporarily unavailable
>> Is this expected behavior?
> The attached works for me and so does my original problem. Can you confirm it resolves your problem? If so I'll send a formal patch.

Seems to fix my problem, thanks.

To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to
More majordomo info at

Powered by blists - more mailing lists