--- Begin Message ---Yeah.To attach to custom bridge create a loopback interface on your host OS, then join custom bridge with loopback, then bridge VBOX VM with loopback.
--- End Message ---
--- Begin Message ---On 01/13/2015 06:39 PM, Alexey Eromenko wrote: > > Yeah. > > To attach to custom bridge create a loopback interface on your host > OS, then join custom bridge with loopback, then bridge VBOX VM with > loopback. > Hello Alexey, What exact loopback device you are referring to here ? Like I mentioned in the initial post, I am able to bind the VMs network to the host's bridge, which isn't bound to any particular host interface. See config below: # This bridge will is used to NAT LXC containers' traffic auto lxcbr0 iface lxcbr0 inet static bridge_fd 0 bridge_maxwait 0 address 172.16.10.1 netmask 255.255.0.0 pre-up brctl addbr lxcbr0 post-down brctl delbr lxcbr0 post-down echo 0 > /proc/sys/net/ipv4/ip_forward post-down echo 0 > /proc/sys/net/ipv6/conf/all/forwarding post-up echo 1 > /proc/sys/net/ipv4/ip_forward post-up echo 1 > /proc/sys/net/ipv6/conf/all/forwarding post-up iptables -A FORWARD -i lxcbr0 -s 172.16.10.1/16 -j ACCEPT post-up iptables -A POSTROUTING -t nat -s 172.16.10.1/16 -j MASQUERADE # add checksum so that dhclient does not complain. # udp packets staying on the same host never have a checksum filled else post-up iptables -A POSTROUTING -t mangle -p udp --dport bootpc -s 172.16.10.1/16 -j CHECKSUM --checksum-fill pre-down iptables -D FORWARD -i lxcbr0 -s 172.16.10.1/16 -j ACCEPT pre-down iptables -D POSTROUTING -t nat -s 172.16.10.1/16 -j MASQUERADE # add checksum so that dhclient does not complain. # udp packets staying on the same host never have a checksum filled else pre-down iptables -D POSTROUTING -t mangle -p udp --dport bootpc -s 172.16.10.1/16 -j CHECKSUM --checksum-fill Can anyone shed some light on what the crash maybe ? I encountered the crash when trying to ssh into one of the VMs, which is when it lost network. Surprisingly, prior to the ssh, all ping requests worked fine. -- Ritesh Raj Sarraf RESEARCHUT - http://www.researchut.com "Necessity is the mother of invention."
signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---Loopback = TAP interface. You will need to create a TAP interface, and it needs to be connected both to Virtual Box and to your bridge. I described exactly how to do this in SUSE lessons for lizards text in 2007, but it is hard to come by nowadays.
--- End Message ---
--- Begin Message ---A simpler way may be to use Virtual Box host-only adapter interface, and add it to your bridge.
--- End Message ---
--- Begin Message ---On 01/13/2015 07:19 PM, Alexey Eromenko wrote: > A simpler way may be to use Virtual Box host-only adapter interface, > and add it to your bridge. Yeah.. But my requirement is different. I'd like to be able to make my LXC containers be on the same bridge, and talk to my VBox VMs. I think I've built the right config. But there's some bug somewhere, because if the config was incorrect, it'd never work. In my case, it works. But later, it dies..... -- Ritesh Raj Sarraf RESEARCHUT - http://www.researchut.com "Necessity is the mother of invention."
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---On 01/14/2015 12:32 AM, Ritesh Raj Sarraf wrote: > On 01/13/2015 07:19 PM, Alexey Eromenko wrote: >> A simpler way may be to use Virtual Box host-only adapter interface, >> and add it to your bridge. > > Yeah.. But my requirement is different. And someone on this please explain what this crash may be at: [ 2289.915168] nspr-3[13830]: segfault at 18 ip 00007f4d559a33af sp 00007f4d45930690 error 4 in VBoxXPCOMIPCC.so[7f4d55991000+1e000] I was able to trigger it again. -- Ritesh Raj Sarraf RESEARCHUT - http://www.researchut.com "Necessity is the mother of invention."
Description: OpenPGP digital signature
--- End Message ---
signature.asc
Description: OpenPGP digital signature
