On Tue 25 Oct 2016 at 12:36:11 +0200, to...@tuxteam.de wrote: > On Tue, Oct 25, 2016 at 10:59:20AM +0100, Brian wrote: > > On Tue 25 Oct 2016 at 11:16:49 +0200, to...@tuxteam.de wrote: > > > > > > lo Link encap:Local Loopback > > > > inet addr:127.0.0.1 Mask:255.0.0.0 > > > > > > This is the "local" interface. It's always there. It doesn't correspond > > > to any hardware. For our quest, you can safely ignore that. > > > > Nothing to do with the OP's issue but people might be interested in > > knowing that this stanza is not a requirement for inclusion in the > > interfaces file. If it is left out you still get a loopback interface. > > > > >From the changelog: > > > > * Add implicit loopback device definition. > > > > -- Andrew Shadura <andre...@debian.org> Thu, 11 Apr 2013 21:44:23 +0200 > > To add some context, this is from ifupdown's (0.7.41) changelog, right?
Sorry; yes. In the final Stretch installer netcfg is quite likely not to put loopback in /etc/network/interfaces. So from being "always there" it will go to never there. -- Brian.
