From 1a29422c086bc45c31c5b427e4053b45f11e2213 Mon Sep 17 00:00:00 2001 From: Sheng Yang Date: Fri, 27 Apr 2012 14:11:48 -0700 Subject: [PATCH] CS-14421: Fix default interfaces file I can't see why we set eth0 to dhcp by default. It would result in eth0 want to get a DHCP address from outside. We should always assign ip through cloud-early-config for it. But one point is, the priority of cloud-early-config and networking script is the same. So even networking got some ip from outside, cloud-early-config should able to override it(if cloud-early-config runs after networking) or networking script won't get dhcp (if cloud-early-config runs before networking), so I am not quite understand why router would get DHCP address in fact. Maybe there are other issues. --- patches/systemvm/debian/config/etc/init.d/cloud-early-config | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/patches/systemvm/debian/config/etc/init.d/cloud-early-config b/patches/systemvm/debian/config/etc/init.d/cloud-early-config index d3aefbe4788..6033402b458 100755 --- a/patches/systemvm/debian/config/etc/init.d/cloud-early-config +++ b/patches/systemvm/debian/config/etc/init.d/cloud-early-config @@ -700,7 +700,7 @@ setup_default() { auto lo eth0 iface lo inet loopback -iface eth0 inet dhcp +iface eth0 inet static EOF }