qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org, sol10x86@cox.net
Subject: Re: [Qemu-devel] Dynamic bridging
Date: Wed, 18 May 2005 13:55:50 +0100	[thread overview]
Message-ID: <200505181355.50450.paul@codesourcery.com> (raw)
In-Reply-To: <20050518005250.PPLV11036.lakermmtao01.cox.net@smtp.east.cox.net>

On Wednesday 18 May 2005 01:52, Ben Taylor wrote:
> I was trying to get the bridging working (with the help
> of pbrook and nox- on the irc #qemu channel) and
> eventually got it working under Sun JDS/3 (Suse 9.1)
> after adding the bridge-util's rpm.
>
> After some experimentation, I found that once I setup
> the bridge on my primary interface, (eth0) and I used
> the qemu-ifup script, the tunnels would automatcially
> attach to the bridge, and when qemu shuts down, they
> automatically go away.
>
> primary-ifup
> Code:
>
> #!/bin/sh
> /sbin/brctl addbr br0
> /sbin/ifconfig eth0 0.0.0.0 promisc up
> /sbin/ifconfig eth0 192.168.1.2 netmask 255.255.255.0 broadcast \
>   192.168.1.255 up

This line should be changes to ifconfig br0 ...., and moved to the end of the 
script. 

You shouldn't give the component devices an IP address, just the br interface. 
Using the component interfaces directly is liable to lead to weird problems 
on the host.

Also, if youdon't want to use a static IP, you can just run dhclient
(or equivalent) on the br0 interface as normal.

My setup looks someting like:

/sbin/brctl addbr br0
/sbin/ifconfig eth0 0.0.0.0 up
/sbin/brctl addif br0 eth0
dhclient br0

Paul

      reply	other threads:[~2005-05-18 13:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-18  0:52 [Qemu-devel] Dynamic bridging Ben Taylor
2005-05-18 12:55 ` Paul Brook [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=200505181355.50450.paul@codesourcery.com \
    --to=paul@codesourcery.com \
    --cc=qemu-devel@nongnu.org \
    --cc=sol10x86@cox.net \
    /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).