From: Ratan Gupta <ratagupt@linux.vnet.ibm.com>
To: openbmc@lists.ozlabs.org
Subject: Re: Default Gateway for a system v/s Default gateway per Interface
Date: Mon, 27 Apr 2020 16:41:15 +0530 [thread overview]
Message-ID: <32f161d2-784e-8fe5-a00b-e9bec181a265@linux.vnet.ibm.com> (raw)
In-Reply-To: <CAPnigKkaj5aU-3KXKsL_LxAdZg2pccXiQz0bPPb+h8RToBzotg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1572 bytes --]
Thanks Patrick, William for sharing the feedbacks
I will start working on the changes.
On 4/24/20 11:15 PM, William Kennington wrote:
> Sounds good to me, we have needed this for a long time because the
> current gateway configuration breaks our v6 stack with multiple NICs.
>
> On Fri, Apr 24, 2020 at 8:21 AM Patrick Williams <patrick@stwcx.xyz
> <mailto:patrick@stwcx.xyz>> wrote:
>
> On Fri, Apr 24, 2020 at 08:36:26PM +0530, Ratan Gupta wrote:
> > ~~~~~~~~~~~~~
> > Kernel IP routing table
> > Destination Gateway Genmask Flags MSS
> Window irtt
> > Iface
> > 0.0.0.0 19.168.2.1 0.0.0.0 UG 0 0 0
> > eth0
> > 0.0.0.0 10.10.10.1 0.0.0.0 UG 0 0 0
> > eth1
> > ~~~~~~~~~~~~~~
> >
> > Kernel will first try using the default gateway having higher
> metric
> > value and then fall back to the lower.
>
> I'm not seeing us with an interface to adjust the metric for an
> interface. I think we need to add that at the same time?
>
Not now, As per my testing if metric value is not defined and both the
routes
having same metric then kernel tries one after other. We can bring the
metric
later.
> Otherwise, I
> don't think we have a way to specify which interface
> outside-the-subnet
> should go (vs today we can set the default-gateway to the desired
> interface's gateway).
> --
> Patrick Williams
>
[-- Attachment #2: Type: text/html, Size: 3061 bytes --]
next prev parent reply other threads:[~2020-04-27 11:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-24 15:06 Default Gateway for a system v/s Default gateway per Interface Ratan Gupta
2020-04-24 15:21 ` Patrick Williams
2020-04-24 17:45 ` William Kennington
2020-04-27 11:11 ` Ratan Gupta [this message]
2020-04-27 19:30 ` Johnathan Mantey
2020-04-28 15:16 ` Ratan Gupta
2020-04-28 18:49 ` Johnathan Mantey
2020-05-04 13:38 ` Ratan Gupta
2020-05-04 16:14 ` Johnathan Mantey
2020-05-06 15:24 ` Patrick Williams
2020-05-08 6:35 ` Ratan Gupta
2020-05-08 17:42 ` Johnathan Mantey
2020-04-28 21:18 ` Patrick Williams
2020-05-04 11:02 ` Andrew Jeffery
2020-06-16 18:02 ` Johnathan Mantey
2020-06-19 22:40 ` Alexander Amelkin
2020-06-23 9:10 ` Ratan Gupta
2020-06-23 10:56 ` 郁雷
2020-06-23 12:57 ` Ratan Gupta
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=32f161d2-784e-8fe5-a00b-e9bec181a265@linux.vnet.ibm.com \
--to=ratagupt@linux.vnet.ibm.com \
--cc=openbmc@lists.ozlabs.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.