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@lists.sourceforge.net > 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/ _______________________________________________ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
