From: "David S. Ahern" <daahern@cisco.com>
To: Dan Johansson <kvm@dmj.nu>
Cc: kvm@vger.kernel.org
Subject: Re: Networkconfiguration with KVM
Date: Mon, 05 Apr 2010 12:34:51 -0600 [thread overview]
Message-ID: <4BBA2D4B.2030303@cisco.com> (raw)
In-Reply-To: <201004052004.34244.kvm@dmj.nu>
On 04/05/2010 12:04 PM, Dan Johansson wrote:
> Must I specify an IP for the br-eth3 interface?
You do not have to specify an IP address for the bridge.
In my case:
mainbr0 Link encap:Ethernet HWaddr <mac>
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:7328933 errors:0 dropped:0 overruns:0 frame:0
TX packets:6992 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:481076877 (458.7 MiB) TX bytes:629184 (614.4 KiB)
tap0 Link encap:Ethernet HWaddr <mac>
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:139390 errors:0 dropped:0 overruns:0 frame:0
TX packets:7460821 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:13554808 (12.9 MiB) TX bytes:601113602 (573.2 MiB)
# brctl show
bridge name bridge id STP enabled interfaces
mainbr0 8000.<mac> no tap0
eth0
eth0 is the interface connected to the physical LAN. mainbr0 ties the
VM's tap to eth0.
David
>
> Regards,
next prev parent reply other threads:[~2010-04-05 18:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-04 12:17 Networkconfiguration with KVM Dan Johansson
2010-04-04 13:00 ` sudhir kumar
2010-04-04 18:02 ` Dan Johansson
2010-04-04 20:23 ` Held Bernhard
2010-04-05 10:09 ` Dan Johansson
[not found] ` <z2sbb653c6e1004050434g209dcc0cmc330c2e391cd68d4@mail.gmail.com>
2010-04-05 14:35 ` Dan Johansson
2010-04-05 16:00 ` David Mair
[not found] ` <4BBA024A.7060504@mgpi.de>
2010-04-05 16:25 ` Dan Johansson
[not found] ` <4BBA2281.906@mgpi.de>
2010-04-05 18:04 ` Dan Johansson
2010-04-05 18:34 ` David S. Ahern [this message]
2010-04-05 20:04 ` Held Bernhard
2010-04-11 15:41 ` Dan Johansson
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=4BBA2D4B.2030303@cisco.com \
--to=daahern@cisco.com \
--cc=kvm@dmj.nu \
--cc=kvm@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 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.