Hi,
I think I had a similar problem. To solve the problem first you need to
set up a bridge, there's instructions in lots of places on how to do this,
auto br0
iface br0 inet static
address 192.168.1.2
network 192.168.1.0
netmask 255.255.255.0
# broadcast 192.168.0.255
gateway 192.168.1.1
bridge_ports eth0
bridge_fd 0
# bridge_hello 2
# bridge_maxage 12
bridge_stp off
Then you need to alter the VM's xml file,
<interface type='bridge'>
<mac address='52:54:00:87:97:a6'/>
<source bridge='br0'/>
Hope this helps, and if you need any more information, just ask
James
On 14/09/12 00:48, lee wrote:
Rob Owens<row...@ptd.net> writes:
On Thu, Sep 13, 2012 at 10:32:40PM +0200, lee wrote:
Hi,
since I'm not making any progress: I want to set up a VM (running
testing) that can be reachable from the outside over the network. I've
done that 2 years or so ago and I forgot how to do the networking setup,
and network configuration has changed in the meantime.
I need to somehow set up a bridge interface so the guest can tap into
it. I don't understand the docs I found about that. Looking at [1], I
can see that my physical network adaptor won't have an IP address
anymore and that there is only a bridge interface instead. This is
probably not what I want, and I remember I did it differently before,
after lots of experimenting.
If you're using Virtualbox, you don't need to set up a bridged interface
with regular Linux tools. You can just select "Bridged networking" for
your virtual machine and Virtualbox handles it.
In older versions of Virtualbox, it was necessary to set up a bridged
interface using Linux tools. Their documentation covered it fairly well
as I recall. I think that was in the version 1.x days. Maybe you can
find some of their old documentation.
Oh I should have mentioned that I'm not using Virtualbox but qemu/kvm or
how it's called. That seems to suggest using a bridge[1], and I find
that very confusing. I understand that apparently I am supposed to
replace my currently used eth1 by a bride device which uses eth1 and to
which I could add other physical devices like eth0. I don't understand
what the purpose of adding more physical devices would be and what I
actually get when I have such a bridge device and what all that has to
do with a guest.
It seems to me that having the bridge device in theory would somehow
magically enable me to give the guest an IP address in the same network
as the host is. That isn't what I want because I want the guest behind
the firewall which is on the host (using shorewall). Of course, I also
don't want to compromise eth1 in any way and don't want to have my
firewall somehow penetrated, which I have no idea about whether it could
happen or not with introducing a bridge device.
I don't get it, it doesn't make any sense to me. At this point, I don't
even know what questions I need to ask.
[1]: ... or allowing the guest access to a physical network card, about
which I don't know whether my hardware would support it or not ---
and I'd have to buy a network cable and plug that into the router
in which case the guest still won't be behind the firewall of the
host
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/5055c5b4.2020...@googlemail.com
