You could upload the vhd as a new template, mark it as 'routing' and set the global config option for routers to the new template.
Erik Den tirsdag 16. juni 2015 skrev Stephan Seitz < s.se...@secretresearchfacility.com> følgende: > Hi there, > > we'ld like to connect to virtualrouters[1] via l2tp/ipsec vpn. In > general, this works as expected, except vpn-clients are unable to > use the virtualrouter as DNS-Server (which is correctly propagated to > the vpn-clients). > > Inside the VR, /etc/dnsmasq.conf shows > interface=eth0 > except-interface=eth1 > except-interface=eth2 > except-interface=lo > listen-address=10.254.254.1 > > ppp0 is never covered by that configuration. > > As a quick fix, I removed the interface= and listen-address= line. > To get rid of those lines, I also removed them in /etc/dnsmasq.conf.tmpl > and commented one dnsmasq.conf-related sed > in /etc/init.d/cloud-early-config. > > > I did the very same changes inside the 4.5 systevm-template. I used > blktap to get access to the vhd. > > All I did shows no effect to the VRs. Every deployment seems completely > unaltered, so I'ld like to ask how (and where) I'm able to patch ( or > personalize ) my router-VMs. > > > Thank's for any suggestions! > > cheers, > - Stephan > > > > [1] root@r-55-VM:~# cat /etc/cloudstack-release > Cloudstack Release 4.5.1 Tue May 5 00:33:58 UTC 2015 > > > >
