All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: netdev@vger.kernel.org
Subject: Fw: [Bug 107071] New: ip route add with src failes with RTNETLINK answers: Invalid argument
Date: Tue, 3 Nov 2015 13:08:20 -0800	[thread overview]
Message-ID: <20151103130820.3356b6cd@xeon-e3> (raw)

This is a 4.3 kernel bug, not iproute2

Begin forwarded message:

Date: Tue, 3 Nov 2015 04:37:03 +0000
From: "bugzilla-daemon@bugzilla.kernel.org" <bugzilla-daemon@bugzilla.kernel.org>
To: "shemminger@linux-foundation.org" <shemminger@linux-foundation.org>
Subject: [Bug 107071] New: ip route add with src failes with RTNETLINK answers: Invalid argument


https://bugzilla.kernel.org/show_bug.cgi?id=107071

            Bug ID: 107071
           Summary: ip route add with src failes with RTNETLINK answers:
                    Invalid argument
           Product: Networking
           Version: 2.5
    Kernel Version: 4.3.0
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: IPV4
          Assignee: shemminger@linux-foundation.org
          Reporter: vladi@aresgate.net
        Regression: No

when I try to add sudo ip route add 10.248.5.0/24 dev bond0.250 table vlan_250
src 10.248.5.154

I get RTNETLINK answers: Invalid argument

On latest 4.3 compiled from source on ubuntu 14.04

strace:
https://bpaste.net/show/78afc27a1bb7

-- 
You are receiving this mail because:
You are the assignee for the bug.

             reply	other threads:[~2015-11-03 21:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-03 21:08 Stephen Hemminger [this message]
2015-11-03 22:21 ` Fw: [Bug 107071] New: ip route add with src failes with RTNETLINK answers: Invalid argument David Ahern

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=20151103130820.3356b6cd@xeon-e3 \
    --to=stephen@networkplumber.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.