Hi, On 1 October 2014 14:49, <[email protected]> wrote: > hm, my isn't. > > What could the difference between your setup and mine be? > > version of ifupdown running: > ifup --version > ifup version 0.7.47.2ubuntu4 > Copyright (c) 1999-2009 Anthony Towns > Copyright (c) 2010-2013 Andrew Shadura > > I've looked through the source and it seems that version 0.7.41 changed > ifupdown to do "noop" on loopbacks which would explain the behaviour i see.
It's not exactly no-op. 7.216 + -ip link set up dev %iface% 2>/dev/null \ 7.217 + if (iface_is_lo()) The interface is brought up when an internal ‘link’ method is executed. Subsequent calls to a loopback method therefore are no-op by default, as the interface is already configured by that point. > I'm curious as to why this was changed though since i don't think it's the > expected behaviour to ignore the request. > http://anonscm.debian.org/hg/collab-maint/ifupdown/rev/1ff1adb9ea06 > --no-loopback > Disable special handling of the loopback interface. By default, the > loopback interface (lo on Linux) is predefined internally as an auto > interface, so it's brought up on ifup -a automatically. In the case the > loopback device is redefined by user, the interface is configured just once > anyway. If, however, another interface is also defined as loopback, it's > configured as usual. Specifying this option disables this behaviour, so > the loopback interface won't be configured automatically. This comment explains this in detail. It should work unless something is broken. > Another server that's running 0.7.8 (Debian wheezy) is managing loopback as > expected: > ifup --version > ifup version 0.7.8 > Copyright (c) 1999-2007 Anthony Towns In that version this code works differently, indeed. -- Cheers, Andrew -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
