Hi Boris,
I been able to setup my guest to use
Host Interface and bridged interface on host.
On Host, tap0 is the "default gateway" for the guest.
I create bridge0 on host, and add to it eth0 and tap0.
So that br0 becomes host's interface to outside world,
eth0 is ifconfig'ed down, and firewall rules are setup
to do the ip-fo accomrwarding and NAT'ing.
I would have absolutely NO idea how I could accomplish
all this on a windows host!
Regards,
JD
Boris wrote:
Hej JD,
thanks a lot for your comment!
As you can see in the description, the vbox uses a Host interface:
NIC 1: MAC: 080027C75C05, Attachment: Host Interface, Cable
connected: on, Trace: off (file: <NULL>), Type: Am79C973
The host is Debian etch without any paket filter. Connecting to internet
through a stand-alone router/firewall, my loved leaf.sourceforge.net. I
have already some experiences with this kind of configuration (with vbox
1.4 on kernel 2.6.18) at least the differences are the newer vbox 1.57
and kernel 2.6.23 ....
I thought about the internal WinXP Firewall, which is still enabled, but
a Windows host is pingable also with enabled filter....
Regards,
Boris
JD schrieb:
In the VM configuration, what network type
are you selecting? NAT or Host Interface?
If you are using Host Interface,
host firewall rules must allow IP forwarding.
If you want to connect from some other external host,
with the guest OS, then you will need to do port-forwarding
on the host that is hosting your guest.
Without good knowledge of networking, you will have a
hard time with connect to your guest from/to other machines.
Good luck,
JD
Boris wrote:
Hej all,
I'm new to this list, so first I want to introduce myself. I'm working
in North-Germany, providing services to some people who are interested
in migrating from propietary systems to opensource. I'm doing mainly
with Debian Linux. I want to thank the devellopers of virtualbox - great
software!
Now here we go:
I have difficulties with a virtualbox (vbox) on a remote server running
Debian Etch with custom kernel 2.6.23.17. It's a headless system and the
vbox is connected with rdp only.
I have difficulties with the host networking: The vbox comes up,
requests and accepts an IP from dhcp (separate dhcpd on different
machine) but is not pingable by any other host.
Here is what I have:
The vbox:
VirtualBox Command Line Management Interface Version 1.5.6
(C) 2005-2008 innotek GmbH
All rights reserved.
Name: WindowsXP_1
Guest OS: Other/Unknown
UUID: f3627eb8-6622-4abd-8495-3711e38e02e2
Config file:
/disk1/vbox/.VirtualBox/Machines/WindowsXP_1/WindowsXP_1.xml
Memory size: 128MB
VRAM size: 8MB
Boot menu mode: message and menu
ACPI: on
IOAPIC: off
Time offset: 0 ms
Hardw. virt.ext: off
State: running (since 2008-04-11T09:58:13.312000000)
Monitor count: 1
Floppy: empty
Primary master: /disk1/vbox/.VirtualBox/VDI/WindowsXP_1.vdi (UUID:
b229fb99-88e8-493e-4ebb-34754d9c7565)
DVD: /usr/share/virtualbox/VBoxGuestAdditions.iso (UUID:
5940b030-abeb-4505-88bb-65493d88a23d)NIC 1: MAC: 080027C75C05,
Attachment: Host Interface, Cable connected: on, Trace: off (file:
<NULL>), Type: Am79C973
NIC 2: disabled
NIC 3: disabled
NIC 4: disabled
UART 1: disabled
UART 2: disabled
Audio: disabled (Driver: Unknown)
Clipboard Mode: Bidirectional
Video mode: 640x480x0
VRDP: enabled (Port 3389, Authentication type: null)
USB: disabled
USB Device Filters:
<none>
Available remote USB devices:
<none>
Currently Attached USB Devices:
<none>
Shared folders: <none>
VRDP Connection: not active
Clients so far: 0
The /etc/network/interfaces:
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
auto eth0
iface eth0 inet manual
pre-up ifconfig $IFACE up
post-down ifconfig $IFACE down
# Dieser Eintrag ist fuer die VirtualBox
auto tap0
iface tap0 inet manual
up ifconfig $iface 192.168.40.201 up
down ifconfig $iface down
tunctl_user mike
auto br0
iface br0 inet static
address 192.168.40.200
netmask 255.255.255.0
broadcast 192.168.40.255
gateway 192.168.40.254
bridge_ports eth0 tap0
########################################
# GBit Netzwerk
auto eth1
iface eth1 inet static
address 192.168.41.200
netmask 255.255.255.0
broadcast 192.168.41.255
I made 'mike' a meber of uml-net and
# l /dev/net/tun
crw-rw---- 1 root uml-net 10, 200 2008-04-11 08:06 /dev/net/tun
I would be glad if anybody could help!
Boris
_______________________________________________
vbox-users mailing list
[email protected]
http://vbox.innotek.de/mailman/listinfo/vbox-users
_______________________________________________
vbox-users mailing list
[email protected]
http://vbox.innotek.de/mailman/listinfo/vbox-users
_______________________________________________
vbox-users mailing list
[email protected]
http://vbox.innotek.de/mailman/listinfo/vbox-users
_______________________________________________
vbox-users mailing list
[email protected]
http://vbox.innotek.de/mailman/listinfo/vbox-users
