From: Andreas Schultz <aschultz@tpip.net>
To: David Ahern <dsa@cumulusnetworks.com>, netdev@vger.kernel.org
Subject: Re: [net-next]: unable to add routes to tables
Date: Wed, 19 Aug 2015 12:38:11 +0200 [thread overview]
Message-ID: <55D45C93.7030509@tpip.net> (raw)
In-Reply-To: <55D36AB7.3040005@cumulusnetworks.com>
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
>> ...
>> 172.28.0.0/24 dev vnf-xe1p0 proto kernel scope link src 172.28.0.16
>>
>> and an empty table 100, this works:
>>
>> # ip route add 10.0.0.0/8 via 172.28.0.32 table 100 dev vnf-xe1p0
>>
>> With net-next at commit d52736e24fe2e927c26817256f8d1a3c8b5d51a0, the
>> same command leads to an:
>>
>> # ip route add 10.0.0.0/8 via 172.28.0.32 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.
Andreas
next prev parent reply other threads:[~2015-08-19 10:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-18 16:57 [net-next]: unable to add routes to tables Andreas Schultz
2015-08-18 17:05 ` David Ahern
2015-08-18 17:26 ` David Ahern
2015-08-19 10:38 ` Andreas Schultz [this message]
2015-08-19 18:40 ` [PATCH] net: Fix nexthop lookups David Ahern
2015-08-20 21:43 ` David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55D45C93.7030509@tpip.net \
--to=aschultz@tpip.net \
--cc=dsa@cumulusnetworks.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).