Do you have any ideas or any way to figure out why loopback isn't
configured at any time on trusty? (even when running ifup lo from
commandline?)
If i understand link.defn correctly "ip link set up dev lo" should be
run if the interface is loopback, but it isn't being run when i test it.
Where in ifup is "method none" in link.defn called?
And isn't this in inet.defn related to the issue?
address_family inet
architecture linux
method loopback
description
This method may be used to define the IPv4 loopback interface.
up
ip link set dev %iface% up if (!iface_is_lo()) << method loopback,
bring interface up if not loopback?
down
ip link set dev %iface% down if (!iface_is_lo()) << same
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.
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]