Netdev Archive on
help / color / mirror / Atom feed
From: hui wang <>
Subject: question about configuring multiple interfaces on a host within the same ipv6 sub-net
Date: Fri, 23 Jul 2021 23:15:19 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Hi All

I have an host (running centos8), it has multiple interfaces connecting 
to the same IPv6 sub-net. Different IPv6 addresses are statically 
assigned to these interfaces. All these interfaces are assigned with the 
same gateway address.

I'd like to config the routing policy so that:

     All packets with source IP address specified goes out via the 
interface where the source IP address was assigned to.
     When source IP address is not specified by application. (ex. TCP 
sync packet), different interfaces' IP address is picked (as source IP 
address) randomly (if the destination IP address is different).

How do I config routing policy to achieve these in such an environment.

Please let me know if there are more appropriate mail lists for my question.



  parent reply	other threads:[~2021-07-24  6:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-24  1:01 IPSec questions and comments Corey Minyard
2021-07-24  2:40 ` Eyal Birger
     [not found] ` <>
2021-07-24  6:15   ` hui wang [this message]
2021-07-25  2:32     ` question about configuring multiple interfaces on a host within the same ipv6 sub-net hui wang
2021-07-26  8:13 ` IPSec questions and comments Steffen Klassert

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).