From: Andrew Morton <akpm@linux-foundation.org>
To: netdev@vger.kernel.org
Cc: "bugme-daemon@kernel-bugs.osdl.org"
<bugme-daemon@kernel-bugs.osdl.org>,
bugzilla@fire.lp0.eu
Subject: Re: [Bugme-new] [Bug 8755] New: "ip -6 route change " behaves like "ip -6 route add"
Date: Sat, 14 Jul 2007 21:47:31 -0700 [thread overview]
Message-ID: <20070714214731.baf38cb8.akpm@linux-foundation.org> (raw)
In-Reply-To: <bug-8755-10286@http.bugzilla.kernel.org/>
On Sat, 14 Jul 2007 15:21:21 -0700 (PDT) bugme-daemon@bugzilla.kernel.org wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=8755
>
> Summary: "ip -6 route change " behaves like "ip -6 route add"
> Product: Networking
> Version: 2.5
> Platform: All
> OS/Version: Linux
> Tree: Mainline
> Status: NEW
> Severity: normal
> Priority: P1
> Component: IPV6
> AssignedTo: yoshfuji@linux-ipv6.org
> ReportedBy: bugzilla@fire.lp0.eu
>
>
> The "ip -6 route change" command behaves as though "ip -6 route add" was used.
> The source of iproute2 shows that "change" uses the "NLM_F_REPLACE" netlink
> flag only.
>
> ip utility, iproute2-ss070313
>
> Changing an existing route:
> # ip -6 r show 2002::/16
> 2002::/16 dev sit0 metric 1024 expires 4482618sec mtu 1480 advmss 7140
> hoplimit 4294967295
> # ip -6 r change 2002::/16 dev sit0 mtu 1280
> RTNETLINK answers: File exists
>
> Adding a route using "change":
> # ip -6 r change 2002::/17 dev sit0 mtu 1280
> # ip -6 r show 2002::/17
> 2002::/17 dev sit0 metric 1024 expires 21334368sec mtu 1280 advmss 1220
> hoplimit 4294967295
>
next parent reply other threads:[~2007-07-15 4:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-8755-10286@http.bugzilla.kernel.org/>
2007-07-15 4:47 ` Andrew Morton [this message]
2007-07-15 15:07 ` [Bugme-new] [Bug 8755] New: "ip -6 route change " behaves like "ip -6 route add" Patrick McHardy
2007-07-15 18:49 ` Simon Arlott
2007-07-16 13:01 ` Patrick McHardy
2007-07-16 18:05 ` Simon Arlott
2007-07-19 18:29 ` Simon Arlott
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=20070714214731.baf38cb8.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bugme-daemon@kernel-bugs.osdl.org \
--cc=bugzilla@fire.lp0.eu \
--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).