tag:blogger.com,1999:blog-3925050740894615221.post7514242891867372211..comments2009-02-11T21:58:04.657ZJulianhttp://www.blogger.com/profile/16293799532055615971noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-3925050740894615221.post-39651620135132588922009-02-11T21:58:00.000Z2009-02-11T21:58:00.000ZAnd one final update!<BR/><BR/>You no longer need to go through all of the above messing about. The latest versions of VirtualBox simply work! Select Host Networking and choose a network interface - done.<BR/><BR/>This works for both Windows and LINUX.<BR/><BR/>Regards, Julian.Julianhttp://www.blogger.com/profile/16293799532055615971noreply@blogger.comtag:blogger.com,1999:blog-3925050740894615221.post-3887518261312060702008-08-26T11:25:00.000+01:002008-08-26T11:25:00.000+01:00I'll post my own comments as it saves me editing the article all the time.<BR/><BR/>You can use the command: "brctl show" (as root) to see if the vbox0 virtual network card is actually attached to the bridge.<BR/><BR/>You can also use the command "netstat -rn" (as root) to see whether you have the correct default routes.<BR/><BR/>Rather than adding a global default route, you can add default routes to each interface. I added them to eth0, eth1 and br0. Doing this enabled me to have the default external traffic going through eth0 which is what I wanted (with vbox traffic going through eth1/br0) - using a global default pushed everything through the bridge for some reason.<BR/>The files are called ifroute-eth0, ifroute-eth1 and ifroute-br0 and all contain:<BR/>"default 192.168.1.1 - ".<BR/><BR/>Regards, Julian.Julianhttp://www.blogger.com/profile/16293799532055615971noreply@blogger.com