From: Jan Kiszka <jan.kiszka@siemens.com>
To: Gerhard Wiesinger <lists@wiesinger.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: [Qemu-devel] Re: Network bridging without adding bridge with brctl, possible?
Date: Thu, 24 Feb 2011 08:50:18 +0100 [thread overview]
Message-ID: <4D660DBA.8040208@siemens.com> (raw)
In-Reply-To: <alpine.LFD.2.02.1102240740490.7604@bbs.intern>
On 2011-02-24 07:49, Gerhard Wiesinger wrote:
> On Wed, 23 Feb 2011, Jan Kiszka wrote:
>> Right, but if I set IP(eth0) == IP(macvlan0), I'm able to communicate
>> between macvlan0 and mactapX, thus between guest and host. Just
>> re-checked here, still works (after resolving the usual MAC address mess
>> I caused by configuring manually).
>
> Thnx for the tipp.
>
> Did you use MAC(eth0) == MAC(macvlan0) or MAC(eth0) <> MAC(macvlan0) to
> get it to work?
The latter (I just let macvlan/tap choose their MACs).
>
> OK, that should be possible because of the layer2 "split brain"
> implementation of macvlan/macvtap between lower interface (e.g. eth0) and
> mavlan*/macvtap*. Therefore the macvlan*/macvtap* interfaces see only each
> other and the outer world/eth0 is another distinct layer2 domain.
>
> My only concern is about layer3 (IP) and same IP address on the same host.
> Because of the "split brain" there shouldn't be any problem from the
> macvlan*/macvtap* point of view and also from the eth0 outside world view.
>
> But from the view of "localhost"/iptables/routing the kernel sees 2
> identical IP addresses. Which one is used on a local ping or local
> connect?
None of both, rather the lookback interface.
Jan
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2011-02-24 7:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-19 19:32 [Qemu-devel] Network bridging without adding bridge with brctl, possible? Gerhard Wiesinger
2011-02-20 9:44 ` [Qemu-devel] " Jan Kiszka
2011-02-20 10:19 ` Gerhard Wiesinger
2011-02-20 11:19 ` Jan Kiszka
2011-02-20 21:28 ` Arnd Bergmann
2011-02-21 6:12 ` Gerhard Wiesinger
2011-02-20 12:49 ` Gerhard Wiesinger
2011-02-20 14:15 ` Jan Kiszka
2011-02-20 15:19 ` Gerhard Wiesinger
2011-02-20 17:39 ` Jan Kiszka
2011-02-20 20:03 ` Gerhard Wiesinger
2011-02-20 21:33 ` Arnd Bergmann
2011-02-21 6:40 ` Gerhard Wiesinger
2011-02-21 8:44 ` Jan Kiszka
2011-02-21 12:07 ` Arnd Bergmann
2011-02-23 6:38 ` Gerhard Wiesinger
2011-02-23 12:53 ` Jan Kiszka
2011-02-24 6:49 ` Gerhard Wiesinger
2011-02-24 7:50 ` Jan Kiszka [this message]
2011-02-24 8:00 ` Arnd Bergmann
2011-02-23 14:47 ` Arnd Bergmann
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=4D660DBA.8040208@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=arnd@arndb.de \
--cc=lists@wiesinger.com \
--cc=qemu-devel@nongnu.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.