From: Akshat Kakkar <akshat.1984@gmail.com>
To: Michal Kubecek <mkubecek@suse.cz>
Cc: netdev <netdev@vger.kernel.org>
Subject: Re: Unable to create ip alias on bridge interface
Date: Tue, 29 May 2018 16:11:39 +0530 [thread overview]
Message-ID: <CAA5aLPhRMPX_jvJknSDwcGZGsPRBeky_ASbaiekR2fxF-OTj9w@mail.gmail.com> (raw)
In-Reply-To: <20180529102954.r7ayncpopip6dcpr@unicorn.suse.cz>
Thanks.
Thanks a lot for clarifying all this.
On Tue, May 29, 2018 at 3:59 PM, Michal Kubecek <mkubecek@suse.cz> wrote:
> On Tue, May 29, 2018 at 03:39:05PM +0530, Akshat Kakkar wrote:
>> For following commands,
>> ip addr add 10.10.10.1/24 brd + dev br0
>> ip addr add 10.10.10.2/24 brd + dev br0
>> ip addr add 20.20.20.1/24 brd + dev br0
>> ip addr add 20.20.20.2/24 brd + dev br0
>>
>> Both 10.10.10.1 and 20.20.20.1 becomes primary. Which one will be used
>> as source IP?
>>
>> Is it nextHop of route that will decide?
>
> Unless you have an unusual routing setup, yes. When unsure, you can use
> "ip route get ..." which should tell you which route and which source
> address will be used.
>
>> And what about communication in local subnet, say ping to 10.10.10.200
>> and 20.20.20.200? Will source for both will change according to
>> destination IP?
>
> This is the same. Under "normal" circumstances, 10.10.10.1 will be used
> for targets from 10.10.10.0/24 and 20.20.20.1 for targets from
> 20.20.20.0/24.
>
> Michal Kubecek
prev parent reply other threads:[~2018-05-29 10:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-28 9:05 Unable to create ip alias on bridge interface Akshat Kakkar
2018-05-28 12:05 ` Michal Kubecek
2018-05-28 18:20 ` Akshat Kakkar
2018-05-29 9:32 ` Michal Kubecek
2018-05-29 10:09 ` Akshat Kakkar
2018-05-29 10:29 ` Michal Kubecek
2018-05-29 10:41 ` Akshat Kakkar [this message]
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=CAA5aLPhRMPX_jvJknSDwcGZGsPRBeky_ASbaiekR2fxF-OTj9w@mail.gmail.com \
--to=akshat.1984@gmail.com \
--cc=mkubecek@suse.cz \
--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).