On Thu, 2007-11-15 at 15:49 +0300, Danila F wrote:
> Alexey, thank you very much for your reply. This (tap0) method works
> good, as well as one recommended by VB documentation (# VBoxAddIF vbox0
> tux br0).
> The problem is how to make v.machine work at gateway-host. Say we use
> eth0 as default gateway interface for our LAN. After we start vmachine
> with Host Interface Networking on, eth0 stops to serve lan clients and
> serves for vmachine only.
> If the add an additional eth card to our host, it can serve vmachine to
> have direct access to LAN, but in this case vmachine doesn't see default
> gateway interface and therefor can't have internet access.
> In my case, "NAT" network scheme for vmachine can solve my major tasks,
> but I wish I have more flexible solution.
> Maybe Host Interface Networking with routing, not bridging, could
> help...
>
> Best regards!
> Danila
>
> On Mon, 2007-11-12 at 22:53 +0200, Alexey Eremenko wrote:
> > There is great tutorial on network bridging with VirtualBox:
> > http://forgeftp.novell.com/lfl/.html/virtualbox.html
> >
> > See chapter: "Intermediate Topic: Networking via Host Bridging"
> >
> > This tutorial is meant for openSUSE Linux, but I hope you will understand
> > it.
> >
>
>
> _______________________________________________
> vbox-users mailing list
> [email protected]
> http://vbox.innotek.de/mailman/listinfo/vbox-users
FINALLY IT WORKS!
Great thanks to vbox command and Alexey, although the solution was just
invented almost by chance.
I run guest-WindowsXP on host-Debian. The host plays the role of
internet access gateway. The goal is to make guest machine mere LAN
client.
I set "Host Interface Networking" + bridging mode. The trouble was that
the guest did not see inner host eth interface, while seeing other lan
addresses. (Even when I arranged them on two different hardware cards on
the same lan segment.) Finally working scheme is:
# brctl show
bridge name bridge id STP enabled interfaces
br0 8000.000854083283 no eth0
tap0
# ifconfig
br0 ...
inet addr:192.168.0.2 Bcast:192.168.0.255 Mask:255.255.255.0
...
eth0 ...
...
eth1 ... # this is the outer interface
inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0
...
lo ...
...
tap0 ...
...
All ip address assignment is made statically. When I assigned on the
guest the same IP as on br0, the corresponding hardware card worked for
host when the guest was off, and for guest when the guest was on - in
natural matter of things. The solution was just to assing ANOTHER
address at the guest (say 192.168.0.3/24).
I only wonder what is the correct way to set up br0 and tap0 permanently
(preserving them through host rebooting)? Or maybe the most natural way
is just run short script to create them just before VBox start?
Best regards!
Danila
_______________________________________________
vbox-users mailing list
[email protected]
http://vbox.innotek.de/mailman/listinfo/vbox-users
