I'm trying to set up a bridge interface as described in many docs, for instance:
https://help.ubuntu.com/community/OpenVPN
My setup in identical to that one, except obviously I used my GCE internal IP, my GCE gateway for my gateway, and set MTU to 1460.
The funny thing is: I can do this from the command line, but when I do it from boot as a service I become locked out of my console.
Here are the last few lines of the serial console output for my unreachable server after reboot:
Mar 25 06:44:51 ns1 cloud-init[1086]: Cloud-init v. 0.7.7 finished at Fri, 25 Mar 2016 06:44:51 +0000. Datasource DataSourceNone. Up 14.15 seconds
Mar 25 06:44:51 ns1 cloud-init[1086]: 2016-03-25 06:44:51,524 - cc_final_message.py[WARNING]: Used fallback datasource
Mar 25 06:44:51 ns1 systemd[1]: Started Execute cloud user/final scripts.
Mar 25 06:44:53 ns1 kernel: [ 15.680040] br0: port 1(eth0) entered forwarding state
Ubuntu 15.10 test-server ttyS0
ns1 login: Mar 25 06:44:56 ns1 kernel: [ 18.816034] br0: port 2(tap0) entered forwarding state
I suppose I could just start the service in a script after boot, but there must be a better way.
One strange behavior I've noticed that may be relevant is that starting the bride interface from the command line breaks DNS (the nameserver at 169.254.169.254 becomes unreachable), and future connections with the web-based ssh server fail (but continue working in putty).
Any help is much appreciated.