public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>
To: Wolfram Gloger <wg1-Rn4VEauK+AKRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: User feedback
Date: Sun, 07 Oct 2007 09:34:58 -0500	[thread overview]
Message-ID: <4708EE92.3080808@codemonkey.ws> (raw)
In-Reply-To: <20071007121109.13666.qmail-apX3yWB0kgwDWtnaHct1IhJ8j3Mt6MsSG9Ur7JDdleE@public.gmane.org>

Wolfram Gloger wrote:
> Anthony Liguori writes:
>
>   
>> http://kvm.qumranet.com/kvmwiki/AnthonyLiguori/Networking
>>
>> This is for Ubuntu but it probably works in Debian too. It uses NAT
>> instead of bridging and it is what I use on my desktop.
>>     
>
> Good advice, but why use a bridge interface _at all_ in this case?
>   

Because sometimes I launch more than one VM and I also wanted to be able 
to use dhcp in the guest.  But yeah, you're right, you could just 
preconfigure a bunch of tapN devices and that would solve the problem too.

Regards,

Anthony Liguori

> I have the following in /etc/network/interfaces:
>
> iface tap0 inet static
>         address 192.168.0.1
>         netmask 255.255.255.0
> 	pre-up iptables-setup-for-masq
>
> and in my qemu-ifup (or rather kvm-ifup):
>
> #!/bin/sh
> /sbin/ifconfig $1 0.0.0.0 up
> /sbin/ifup $1
> exit 0
>
> and that is all..  No more need for any bridging.
>
> BTW I think it would be an important feature to also have
> a qemu-ifdown / kvm-ifdown script to remove the iptables
> rules after the tap device disappears.
>
> Regards,
> Wolfram.
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> kvm-devel mailing list
> kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> https://lists.sourceforge.net/lists/listinfo/kvm-devel
>
>   


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/

  parent reply	other threads:[~2007-10-07 14:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-07 12:11 User feedback Wolfram Gloger
     [not found] ` <20071007121109.13666.qmail-apX3yWB0kgwDWtnaHct1IhJ8j3Mt6MsSG9Ur7JDdleE@public.gmane.org>
2007-10-07 14:34   ` Anthony Liguori [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-10-05 12:02 rob wilco
     [not found] ` <84ad660e0710050502q3f4a3156g5451f7c70f2f7fdd-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-10-05 12:52   ` Anthony Liguori
     [not found]     ` <47063371.9060105-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>
2007-10-05 14:57       ` John Clemens
2007-10-05 12:56   ` Avi Kivity

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=4708EE92.3080808@codemonkey.ws \
    --to=anthony-rdkfgonbjusknkdkm+me6a@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=wg1-Rn4VEauK+AKRv+LV9MX5uipxlwaOVQ5f@public.gmane.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