lxc postinst incorrectly chooses network address to use

Bug #1358306 reported by LaMont Jones
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
lxc (Ubuntu)
Triaged
Medium
Unassigned

Bug Description

The lxc postinst assumes that only /24 networks are used in 10.0.0.0/8. If the host has a route for 10.0.0.2/23 (or 10.0.0.0/22, or any other block that includes 10.0.3.0/24 or whatever other block it is checking) then the postinst chooses a chunk of the existing network block, breaking connectivity.

Preparing to unpack .../lxc_1.0.5-0ubuntu0.1_amd64.deb ...
Unpacking lxc (1.0.5-0ubuntu0.1) ...
Processing triggers for ureadahead (0.100.0-16) ...
ureadahead will be reprofiled on next reboot
Processing triggers for man-db (2.6.7.1-1) ...
Setting up lxc (1.0.5-0ubuntu0.1) ...
lxc start/running
Setting up lxc dnsmasq configuration.
Processing triggers for ureadahead (0.100.0-16) ...
On branch master
nothing to commit, working directory clean
-soko(root) 308 : netstat -rn | grep ^10.0..\.
10.0.2.0 10.172.64.1 255.255.254.0 UG 0 0 0 tun0
10.0.3.0 0.0.0.0 255.255.255.0 U 0 0 0 lxcbr0

Revision history for this message
Serge Hallyn (serge-hallyn) wrote :

Thanks. This'll need to be fixed in the lxc.preinst.

Changed in lxc (Ubuntu):
importance: Undecided → Medium
status: New → Confirmed
Changed in lxc (Ubuntu):
status: Confirmed → Triaged
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.