[Feisty] LTSP fails on multi-homed server due to network manager touching predefined static interfaces

[Kirk Steffensen]

As documented in bug #96103 https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/96103 the network manager will only activate one nic at a time in a multi-homed host. If you run ifconfig, the second card is there, but there is no IP address assigned to it, even though it has a static address in /etc/network/interfaces. On my system, network manager always starts eth1, the public internet interface, and leaves eth0 down, the LTSP client-side interface.

LTSP's DHCP fails to start because there is no active subnet for the client side.

The work around is to manually "sudo ifdown eth0" and then "sudo ifup eth0". This restores an IP address for the client side. Then run "sudo /etc/init.d/dhcp3-server restart".

This must be manually done on every reboot. I have tried to make a init.d script to automate it, but being a linux newbie, I still haven't been able to get it to work in the right place to come after networking start and before dhcp start.

Please fix for Feisty release. This kills LTSP out of the box. Thanks.

ProblemType: Bug
Architecture: i386
Date: Mon Apr 2 05:50:11 2007
DistroRelease: Ubuntu 7.04
Uname: Linux library 2.6.20-12-386 #2 Wed Mar 21 20:53:13 UTC 2007 i686 GNU/Linux

[Oliver Grawert (ogra)]

added to network manager as well, afaik it is planned to have an override flag in /etc/network/interfaces to make NM not touch these interfaces, the change needs to be added to ltsp's autoconfiguration as soon as this flag exists.

[Tollef Fog Heen (tfheen)]

The NM bits of this has been fixed now, please make sure LTSP now works correctly and close this bug.

[Oliver Grawert (ogra)]

no changes in ltsp required