I tested this by creating a cloud container, temporarily setting USE_LXC_BRIDGE=false, rebooting, building the package, setting USE_LXC_BRIDGE=true (leaving 10.0.3 as the lxcbr0 subnet), rebooting. lxcbr0 comes up with 10.0.4.1 as expected. A nested trusty container works fine.
The package is targeted at wily, should be at xenial presumably. That should be the only needed update.
Debdiff which works for me.
I tested this by creating a cloud container, temporarily setting USE_LXC_ BRIDGE= false, rebooting, building the package, setting USE_LXC_BRIDGE=true (leaving 10.0.3 as the lxcbr0 subnet), rebooting. lxcbr0 comes up with 10.0.4.1 as expected. A nested trusty container works fine.
The package is targeted at wily, should be at xenial presumably. That should be the only needed update.