VirtualBox

Changes between Version 5 and Version 6 of Automatic_Bridge_Ubuntu


Ignore:
Timestamp:
Apr 26, 2007 9:05:56 AM (17 years ago)
Author:
Klaus Espenlaub
Comment:

--

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 ==
    22
    33Version: 0.1[[BR]]
     
    1313when the VM is launched.
    1414
    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 ;)
     15In 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 ;)
    1616
    1717I'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 i get my IP automatically.
     18modem to which I connect through my eth0 port. The modem has DHCP, so I get my IP automatically.
    1919
    2020= 1.1 What is bridging anyway? =
     
    138138
    139139Now 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 and
     140by !VirtualBox every time a VM is turned on/off. I call these scripts tapUP and
    141141tapDown, 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 use
     142same as described in the !VirtualBox User Manual, with the exception that i don't use
    143143sudo (since i did a setuid in ifconfig and brctl).
    144144
     
    188188= 8. TODO =
    189189
    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).
    191191
    192192= 9. References =

© 2023 Oracle
ContactPrivacy policyTerms of Use