Am I correct in thinking that: xenbr0 is required for domU guests to be accessed from the host (via the guest's 192.168.56.x address) ? xenbr1 is required for domU guests to access the internet (via the hosts NAT interface) ?
Any one got any ideas what else needs to be done (e.g. xen configuration) because devcloud's eth0 and eth1 need to be swapped for vagrant? On Sun, Feb 16, 2014 at 11:36 AM, chris snow <chsnow...@gmail.com> wrote: > For the vagrant version of devcloud that I am working on (which may > become devcloud 3?), I have had to switch the network cards in > Virtualbox. > > Devcloud2 has > > eth0 - host only network > eth1 - nat network > > However, Vagrant requires the first network card to be the NAT one, i.e. > > eth0 - nat network > eth1 - host only network > > Question 1: Am I correct in thinking that I just need to make the > following changes to the devcloud2 network setup: > > auto xenbr0 > iface xenbr0 inet static > bridge_ports eth0 # <-- devcloud3 changes this to eth1 > address 192.168.56.10 > netmask 255.255.255.0 > network 192.168.56.0 > broadcast 192.168.56.255 > gateway 192.168.56.1 > dns_nameservers 8.8.8.8 8.8.4.4 > post-up route del default gw 192.168.56.1; route add default > gw 192.168.56.1 metric 100; > > auto xenbr1 > iface xenbr1 inet dhcp > bridge_ports eth1 # <-- devcloud3 changes this to eth0 > dns_nameservers 8.8.8.8 8.8.4.4 > post-up route add default gw 10.0.3.2 # <-- devcloud3 changes > this to 10.0.2.2 > > Question 2: What is the purpose of xenbr0 and xenbr1? I.e. how are > there bridges used by cloudstack / xen? > > Many thanks, > > Chris -- Check out my professional profile and connect with me on LinkedIn. http://lnkd.in/cw5k69
