From: Patrick McHardy <kaber@trash.net>
To: bugzilla@fire.lp0.eu
Cc: Andrew Morton <akpm@linux-foundation.org>,
netdev@vger.kernel.org,
"bugme-daemon@kernel-bugs.osdl.org"
<bugme-daemon@kernel-bugs.osdl.org>
Subject: Re: [Bugme-new] [Bug 8755] New: "ip -6 route change " behaves like "ip -6 route add"
Date: Sun, 15 Jul 2007 17:07:26 +0200 [thread overview]
Message-ID: <469A382E.6000104@trash.net> (raw)
In-Reply-To: <20070714214731.baf38cb8.akpm@linux-foundation.org>
Andrew Morton wrote:
> On Sat, 14 Jul 2007 15:21:21 -0700 (PDT) bugme-daemon@bugzilla.kernel.org wrote:
>
>>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
There is a difference between "add" and "change". "add" will only add a
new address if there isn't already one with the same identity, "change"
will allow to change attributes of an existing address, like flags,
lifetime, ..., or behave similar to "add" in case the address doesn't
already exist.
What kind of behaviour are you expecting?
next prev parent reply other threads:[~2007-07-15 15:08 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 ` [Bugme-new] [Bug 8755] New: "ip -6 route change " behaves like "ip -6 route add" Andrew Morton
2007-07-15 15:07 ` Patrick McHardy [this message]
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=469A382E.6000104@trash.net \
--to=kaber@trash.net \
--cc=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).