Comment 14 for bug 1367495

This is odd. On advice from Flockport community I attempted to manually configure the bridge (its basic elements, at least) by entering
    sudo brctl addbr lxcbr0
    sudo ifconfig lxcbr0 10.0.3.1 netmask 255.255.255.0 up

This went just fine, with `ifconfig` reporting (beyond those interfaces already present in the attached file:
    lxcbr0 Link encap:Ethernet HWaddr 8e:8c:5c:47:3b:bd
              inet addr:10.0.3.1 Bcast:10.0.3.255 Mask:255.255.255.0
              inet6 addr: fe80::8c8c:5cff:fe47:3bbd/64 Scope:Link
              UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
              RX packets:0 errors:0 dropped:0 overruns:0 frame:0
              TX packets:35 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:0
              RX bytes:0 (0.0 B) TX bytes:3632 (3.6 KB)

Note in particular the `inet addr`, which is the same one `lxc-net.log` claimed couldn't be used. However, recycling `lxc-net` fails, either with:
    server@srv-Ub1404:~$ sudo restart lxc-net
    restart: Job failed to restart
Or
    server@srv-Ub1404:~$ sudo stop lxc-net
    stop: Job failed while stopping
    server@srv-Ub1404:~$ sudo start lxc-net
    lxc-net start/running

In both cases, the bridge is gone from the output of `ifconfig` as a result. `/var/log/upstart/lxc-net.log` is exactly as it is in the attached version (complaining about `dnsmasq.conf`, which is understandable, but also about 10.0.3.1 already being in use).