From: Ryan Whelan <rcwhelan@gmail.com>
To: David Ahern <dsahern@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: iproute2 - modifying routes in place
Date: Mon, 14 May 2018 16:10:44 -0400 [thread overview]
Message-ID: <CAM3m09SGxsBhxeQoM8GNjMCryUjpMPqon3OYrdO3_FKmp91z3Q@mail.gmail.com> (raw)
In-Reply-To: <7b4fac83-210f-2e91-5e56-6a381bd2a5ba@gmail.com>
On Mon, May 14, 2018 at 2:49 PM David Ahern <dsahern@gmail.com> wrote:
> On 5/14/18 12:40 PM, Ryan Whelan wrote:
> > Same behavior:
> >
> >
> > root@rwhelan-linux ~
> > # ip -6 route
> > ::1 dev lo proto kernel metric 256 pref medium
> > fd9b:caee:ff93:ceef:3431:3831:3930:3031 dev internal0 proto kernel
metric
> > 256 pref medium
> > fd9b:caee:ff93:ceef:3431:3831:3930:3032 dev internal0 src
> > fd9b:caee:ff93:ceef:3431:3831:3930:3031 metric 1024 pref medium
> > fe80::/64 dev enp0s3 proto kernel metric 256 pref medium
> > fe80::/64 dev enp0s8 proto kernel metric 256 pref medium
> > fe80::/64 dev internal0 proto kernel metric 256 pref medium
> >
> > root@rwhelan-linux ~
> > # ip -6 route change fd9b:caee:ff93:ceef:3431:3831:3930:3032 dev
internal0
> > src fd9b:caee:ff93:ceef:3431:3831:3930:3031 metric 10
> > RTNETLINK answers: No such file or directory
> 'change' only sets NLM_F_REPLACE. Since NLM_F_CREATE is not set ('ip ro
> replace') it does not add a new route and expects one to exist. Your
> table above shows the prefix with metric 256 not metric 10 so the route
> does not match. You should be seeing a message in dmesg to this effect.
Is there a syntax for changing a route in-place? Specifically, i'm
interesting in changing the metric of currently existing routes.
next prev parent reply other threads:[~2018-05-14 20:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-11 11:42 iproute2 - modifying routes in place Ryan Whelan
2018-05-12 17:00 ` David Ahern
2018-05-14 18:40 ` Ryan Whelan
2018-05-14 18:49 ` David Ahern
2018-05-14 20:10 ` Ryan Whelan [this message]
2018-05-14 20:20 ` 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=CAM3m09SGxsBhxeQoM8GNjMCryUjpMPqon3OYrdO3_FKmp91z3Q@mail.gmail.com \
--to=rcwhelan@gmail.com \
--cc=dsahern@gmail.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).