Hi AD, If you have the tunctl command on debian, then all you need are the 3 scripts I am using to make bridged networking work. I will be happy to share them with you.
Difference is that I am using eth0. I do not have eth1. You will have to first undo all the bridge setup and tap setup you have so far. Then you will execute just one script: vboxbr start and when you want to tear it all down: vboxbr stop The caveat is: Once you do the start, you must not invoke any utility or command which will modify networking or the firewall, OK? If you do, it will break the firewall masquerading rules and guest OS will cease communication with the outside world. So, place these 3 scrips somewhere in your PATH. I usually place things like thisn in my ~/bin/ which is in my path, and chmod them to make them executable. And that's it!! Please let me know how it went. Cheers, JD A D wrote:
Now I changed /etc/network/interfaces to this found on internet: # 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 allow-hotplug eth1 iface eth1 inet manual auto tap0 iface tap0 inet manual up ifconfig $IFACE 0.0.0.0 up down ifconfig $IFACE down tunctl_user ad auto br0 iface br0 inet static address 192.168.1.103 network 192.168.1.0 netmask 255.255.255.0 broadcast 192.168.1.255 bridge_ports eth1 tap0 bridge_maxwait 0But now after reboot neither host(Debian Etch) nor guest os(Winxp) can connect to internet. output of route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 br0Am i missing something? Also i have setup winxp to obtain ip address automatically.if that helps. ----------------------------------------Date: Fri, 7 Mar 2008 11:51:07 +0100 From: [EMAIL PROTECTED] To: [email protected] Subject: Re: [vbox-users] Guest OS(Winxp): Unable to connect to internet, network A D wrote: [...]This is a misconfiguration. DO NOT assign any configuration to eth1 if you want to use it in a bridge. Just configure the bridge. If fact you don't even need to mention the physical interface you want to use for bridging anywhere but in the bridge_ports line in the br0 config.# The primary network interface allow-hotplug eth1 iface eth1 inet static address 192.168.1.103 netmask 255.255.255.0 network 192.168.1.0 broadcast 192.168.1.255 gateway 192.168.1.1 # dns-* options are implemented by the resolvconf package, if installed dns-nameservers XXX.XXX.XXX.XXX XXX.XXX.XXX.XXX auto tap0 iface tap0 inet manual up ifconfig $IFACE 0.0.0.0 up down ifconfig $IFACE down tunctl_user ad auto br0 iface br0 inet static address 192.168.1.103 network 192.168.1.0 netmask 255.255.255.0 broadcast 192.168.1.255 gateway 192.168.1.1 bridge_ports eth1 tap0I suspect (the ifconfig output you provide isn't helpful in that context, I'd need the routing table, route -n) that this prevents things from working. Like setting up routes incorrectly.-- Dr. Klaus Espenlaub innotek GmbH, http://www.innotek.de _______________________________________________ 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
vboxbrfiles.tar.bz2
Description: application/bzip
_______________________________________________ vbox-users mailing list [email protected] http://vbox.innotek.de/mailman/listinfo/vbox-users
