Changes between Version 5 and Version 6 of Automatic_Bridge_Ubuntu
- Timestamp:
- Apr 26, 2007 9:05:56 AM (18 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Automatic_Bridge_Ubuntu
v5 v6 1 == HOWTO Automatically configure bridge interfaces on VirtualBox ==1 == HOWTO Automatically configure bridge interfaces on !VirtualBox == 2 2 3 3 Version: 0.1[[BR]] … … 13 13 when the VM is launched. 14 14 15 In fact the Vbox User Manual has all the details that you need to accomplish it, but ithought it would be better to give some more "hands on" for you guys ;)15 In fact the Vbox User Manual has all the details that you need to accomplish it, but I thought it would be better to give some more "hands on" for you guys ;) 16 16 17 17 I've tested this setup in my home computer, running Kubuntu 6.10. I've an ADSL 18 modem to which i connect through my eth0 port. The modem has DHCP, so iget my IP automatically.18 modem to which I connect through my eth0 port. The modem has DHCP, so I get my IP automatically. 19 19 20 20 = 1.1 What is bridging anyway? = … … 138 138 139 139 Now that everything is in place lets configure the scripts that will be called 140 by VBox every time a VM is turned on/off. I call these scripts tapUP and140 by !VirtualBox every time a VM is turned on/off. I call these scripts tapUP and 141 141 tapDown, but you can name them whatever you want. The commands i use are the 142 same as described in the VBox User Manual, with the exception that i don't use142 same as described in the !VirtualBox User Manual, with the exception that i don't use 143 143 sudo (since i did a setuid in ifconfig and brctl). 144 144 … … 188 188 = 8. TODO = 189 189 190 (section added 2007-03-29 by klaus) This description doesn't put eth0 in promisc mode (leads to confusing connectivity problems when ARP requests for the guest and the host don't get through the bridge). Also it could be made a bit clearer what to enter where in the network config dialog (e.g. with a screenshot).190 (section added 2007-03-29 by klaus) This description doesn't put eth0 in promisc mode (leads to confusing connectivity problems when non-boradcast ARP requests for the guest and the host don't get through the bridge). Also it could be made a bit clearer what to enter where in the network config dialog (e.g. with a screenshot). 191 191 192 192 = 9. References =