On Sat 20 Jan 2018 at 12:18:45 -0600, David Wright wrote: > On Fri 19 Jan 2018 at 15:21:31 (+0000), Brian wrote: > > On Fri 19 Jan 2018 at 08:27:22 -0600, David Wright wrote: > > > > > With wireless, there's no real equivalent to the wire > > > being connected. Even when installed and configured with > > > wireless, rebooting doesn't automatically bring up a > > > network; you need to type ifup. > > > > I'm not fine with this. Given a WAP and a passphrase ifupdown connects > > automatically here. Perhaps I'm misunderstanding you. > > Yes, sorry, I misremembered, as it was a while since I'd done > a wireless installation. Here's the results of doing one just > now. It wasn't so much the ifup that was needed as populating > /etc/network/interfaces itself.
Thanks for looking into this. It did provide me with an incentive (I'm no network expert) to spend part of this afternoon plugging every wireless adaptor I possess in and out, in and out .... :) to refresh what my recollection was. It gets a bit more complicated when there is a wired interface too, but I'm not going to go there. > $ cat /etc/network/interfaces > # This file describes the network interfaces available on your system > # and how to activate them. For more information, see interfaces(5). > > source /etc/network/interfaces.d/* > > # The loopback network interface > auto lo > iface lo inet loopback Just for reference: d-i provides this stanza but there is really no need for it (on i386 and amd64, anyway). It does no harm but ifupdown handles setting up the lo interface all by itself without anything in /e/n/i. -- Brian.
