Re: fix for no ssh

From	David Wright <deblis@lionunicorn.co.uk>
Newsgroups	linux.debian.user
Subject	Re: fix for no ssh
Date	2019-07-09 01:30 +0200
Message-ID	<yhLf3-4mI-9@gated-at.bofh.it> (permalink)
References	(5 earlier) <yhy89-4RP-7@gated-at.bofh.it> <yhyrv-4Yr-3@gated-at.bofh.it> <yhyBc-51M-3@gated-at.bofh.it> <yhz4d-5qG-5@gated-at.bofh.it> <yhEGD-nw-19@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

On Mon 08 Jul 2019 at 19:21:37 (+0300), Andrei POPESCU wrote:
> On Lu, 08 iul 19, 10:19:35, Curt wrote:
> > 
> > I thought you were saying that
> > '/etc/udev/rules.d/70-persistent-net.rules' remains a valid mechanism
> > for defining interface names in Buster (fixed). But the release-notes
> > (hmm, I think they've been modified since I last looked and now state
> > that that file is no longer "officially" supported by udev---but may
> > work in some cases). So I wouldn't be filing a bug report against that
> > stanza any longer, as current situation seems unverifiable. 
>  
> For the record, the current wording (no official support) is based on 
> input from the Debian systemd maintainers. They should know what is 
> supported or not ;)
> 
> As far as I know the /etc/udev/rules.d/70-persistent-net.rules method 
> can fail to properly rename the interfaces in certain situations which 
> can leave your system without networking.
> 
> Not nice on remote machines.
> 
> It is also my understanding that systems with only one interface (of a 
> given type[1]) are pretty safe with it or net.ifnames=0, so the impact 
> on regular[2] desktop/laptop users should be minimal.
> 
> [1] assuming ethernet cards are always named ethX and wireless cards are 
> always named wlanX by the kernel. I might have had a wireless card that 
> came up as ethX, but that was a long time ago. Still, something to be 
> aware of.

I'm still running one that comes up in jessie as eth0 and eth1;
stretch gets it right with enp2s2 and wlp2s4 respectively.

> [2] one ethernet interface, usually integrated in the motherboard and 
> one (additional) wireless interface for the laptops. Anything more 
> complicated than that might break without warning.
> 
> > Well, at the very least people should be informed who is likely to be
> > affected by the bug
> 
> In my understanding a lot of daemons are affected. Would it make sense 
> to (try to) list them all?

I guess I don't use my interfaces very adventurously so I don't see
many instances of their names, but one or two look odd. On jessie
(old-style names), and ignoring comments, I see

# grep -r -e '\<eth\>' -e 'eth[01]' /etc/
/etc/wicd/manager-settings.conf:wireless_interface = eth1
/etc/wicd/manager-settings.conf:wired_interface = eth0
/etc/samba/smb.conf:;   interfaces = 127.0.0.0/8 eth0
/etc/samba/dhcp.conf:   wins server =eth1:192.168.6.1
/etc/resolvconf/interface-order:eth*([^.]).inet6
/etc/resolvconf/interface-order:eth*([^.]).ip6.@(dhclient|dhcpcd|pump|udhcpc)
/etc/resolvconf/interface-order:eth*([^.]).inet
/etc/resolvconf/interface-order:eth*([^.]).@(dhclient|dhcpcd|pump|udhcpc)
/etc/resolvconf/interface-order:eth*
/etc/udev/rules.d/70-persistent-net.rules: … … … [obviously]
# 

The wicd settings were entered by myself.
Actually, smb.conf is a comment line (with ;) but I think it was
written from information derived from the system. But dhcp.conf
looks odd because eth1: (my wireless interface) has never seen
a network numbered 192.168.6.0.

Turning to a new stretch installation, I see

# grep -r -e '\<eth\>' -e 'eth[01]' -e 'enp1s0' -e '\<wl' /etc/
/etc/wicd/manager-settings.conf:wireless_interface = wlp2s0
/etc/wicd/manager-settings.conf:wired_interface = enp1s0
/etc/resolvconf/interface-order:@(br|eth)*([^.]).inet6
/etc/resolvconf/interface-order:@(br|eth)*([^.]).ip6.@(dhclient|dhcpcd|pump|udhcpc)
/etc/resolvconf/interface-order:@(br|eth)*([^.]).inet
/etc/resolvconf/interface-order:@(br|eth)*([^.]).@(dhclient|dhcpcd|pump|udhcpc)
/etc/resolvconf/interface-order:@(br|eth)*
/etc/resolvconf/interface-order:@(ath|wifi|wlan)*([^.]).inet6
/etc/resolvconf/interface-order:@(ath|wifi|wlan)*([^.]).ip6.@(dhclient|dhcpcd|pump|udhcpc)
/etc/resolvconf/interface-order:@(ath|wifi|wlan)*([^.]).inet
/etc/resolvconf/interface-order:@(ath|wifi|wlan)*([^.]).@(dhclient|dhcpcd|pump|udhcpc)
/etc/resolvconf/interface-order:@(ath|wifi|wlan)*
/etc/init.d/ifplugd:            eth*|wlan*)
# 

Again, the wicd settings were entered by myself. So the oddity here is
interface-order which has patterns that don't match the interface
names.   man interface-order   doesn't say which directory it should
be run in, but I'm assuming it's going to be something like
/run/resolvconf/interface where I see files called wlp2s0.dhclient
and wlp2s0.wicd. Perhaps I'm off the mark here.

I haven't studied the contents of /etc/init.d/ifplugd, but cut and
pasting the all_interfaces() function into the commandline prints
nothing, whereas editing it eth*|wlan* → en*|wl* makes it report
enp1s0 and wlp2s0, which suggests that that script is just plain wrong.
BTW, I don't actually use ifplugd; I installed it in June during the
"New nomeclature of ethernet devices" thread.

Cheers,
David.

Thread

fix for no ssh Gene Heskett <gheskett@shentel.net> - 2019-07-07 16:30 +0200
  Re: fix for no ssh Tixy <tixy@yxit.co.uk> - 2019-07-07 16:50 +0200
    Re: fix for no ssh Andrei POPESCU <andreimpopescu@gmail.com> - 2019-07-07 18:50 +0200
      Re: fix for no ssh Nicholas Geovanis <nickgeovanis@gmail.com> - 2019-07-07 19:50 +0200
        Re: fix for no ssh Andrei POPESCU <andreimpopescu@gmail.com> - 2019-07-08 09:00 +0200
          Re: fix for no ssh Curt <curty@free.fr> - 2019-07-08 11:10 +0200
            Re: fix for no ssh Andrei POPESCU <andreimpopescu@gmail.com> - 2019-07-08 12:20 +0200
              Re: fix for no ssh Curt <curty@free.fr> - 2019-07-08 13:00 +0200
              Re: fix for no ssh Curt <curty@free.fr> - 2019-07-08 16:50 +0200
                Re: fix for no ssh Greg Wooledge <wooledg@eeg.ccf.org> - 2019-07-08 17:40 +0200
                Re: fix for no ssh Curt <curty@free.fr> - 2019-07-08 18:20 +0200
                Re: fix for no ssh Andy Smith <andy@strugglers.net> - 2019-07-08 18:50 +0200
                Re: fix for no ssh Curt <curty@free.fr> - 2019-07-09 10:20 +0200
                Re: fix for no ssh Andy Smith <andy@strugglers.net> - 2019-07-10 10:20 +0200
                Re: fix for no ssh Curt <curty@free.fr> - 2019-07-10 11:30 +0200
                Re: fix for no ssh Andy Smith <andy@strugglers.net> - 2019-07-10 13:50 +0200
                Re: fix for no ssh Reco <recoverym4n@enotuniq.net> - 2019-07-10 14:30 +0200
                Re: fix for no ssh Greg Wooledge <wooledg@eeg.ccf.org> - 2019-07-10 15:10 +0200
                Re: fix for no ssh Curt <curty@free.fr> - 2019-07-10 16:10 +0200
                Re: fix for no ssh Andy Smith <andy@strugglers.net> - 2019-07-11 14:10 +0200
                Re: fix for no ssh Reco <recoverym4n@enotuniq.net> - 2019-07-11 16:20 +0200
                Re: fix for no ssh Andy Smith <andy@strugglers.net> - 2019-07-11 17:10 +0200
                Re: fix for no ssh Reco <recoverym4n@enotuniq.net> - 2019-07-11 17:20 +0200
                Re: fix for no ssh Curt <curty@free.fr> - 2019-07-10 16:00 +0200
                Re: fix for no ssh David Wright <deblis@lionunicorn.co.uk> - 2019-07-10 21:20 +0200
                Re: fix for no ssh Andrei POPESCU <andreimpopescu@gmail.com> - 2019-07-10 21:30 +0200
                [OT] Trustfulness. Was: Re: fix for no ssh "Thomas Schmitt" <scdbackup@gmx.net> - 2019-07-08 18:00 +0200
                Re: [OT] Trustfulness. Was: Re: fix for no ssh Reco <recoverym4n@enotuniq.net> - 2019-07-08 18:10 +0200
                Re: fix for no ssh Andy Smith <andy@strugglers.net> - 2019-07-08 18:10 +0200
          Re: fix for no ssh Henrique de Moraes Holschuh <hmh@debian.org> - 2019-07-09 01:30 +0200
      Re: fix for no ssh Curt <curty@free.fr> - 2019-07-08 10:50 +0200
        Re: fix for no ssh Andrei POPESCU <andreimpopescu@gmail.com> - 2019-07-08 11:00 +0200
          Re: fix for no ssh Curt <curty@free.fr> - 2019-07-08 11:20 +0200
            Re: fix for no ssh Andrei POPESCU <andreimpopescu@gmail.com> - 2019-07-08 11:30 +0200
              Re: fix for no ssh Curt <curty@free.fr> - 2019-07-08 11:50 +0200
                Re: fix for no ssh Andrei POPESCU <andreimpopescu@gmail.com> - 2019-07-08 12:00 +0200
                Re: fix for no ssh Curt <curty@free.fr> - 2019-07-08 12:30 +0200
                Re: fix for no ssh Andrei POPESCU <andreimpopescu@gmail.com> - 2019-07-08 18:30 +0200
                Re: fix for no ssh Curt <curty@free.fr> - 2019-07-08 19:50 +0200
                Re: fix for no ssh Andy Smith <andy@strugglers.net> - 2019-07-08 20:20 +0200
                Re: fix for no ssh Gene Heskett <gheskett@shentel.net> - 2019-07-08 21:00 +0200
                Re: fix for no ssh Andy Smith <andy@strugglers.net> - 2019-07-08 22:50 +0200
                Fwd: fix for no ssh Nicholas Geovanis <nickgeovanis@gmail.com> - 2019-07-08 23:50 +0200
                Re: Fwd: fix for no ssh Andy Smith <andy@strugglers.net> - 2019-07-09 00:40 +0200
                Re: fix for no ssh John Hasler <jhasler@newsguy.com> - 2019-07-09 01:20 +0200
                Re: fix for no ssh Nicholas Geovanis <nickgeovanis@gmail.com> - 2019-07-09 01:30 +0200
                Re: fix for no ssh Andrei POPESCU <andreimpopescu@gmail.com> - 2019-07-09 09:50 +0200
                Re: fix for no ssh Andrei POPESCU <andreimpopescu@gmail.com> - 2019-07-08 23:00 +0200
                Re: fix for no ssh Andrei POPESCU <andreimpopescu@gmail.com> - 2019-07-08 23:00 +0200
                Re: fix for no ssh Curt <curty@free.fr> - 2019-07-10 09:50 +0200
                Re: fix for no ssh Andrei POPESCU <andreimpopescu@gmail.com> - 2019-07-10 21:40 +0200
                Re: fix for no ssh David Wright <deblis@lionunicorn.co.uk> - 2019-07-09 01:30 +0200
                Re: fix for no ssh Andrei POPESCU <andreimpopescu@gmail.com> - 2019-07-09 10:00 +0200
                Re: fix for no ssh David Wright <deblis@lionunicorn.co.uk> - 2019-07-10 01:20 +0200
                Re: fix for no ssh Andrei POPESCU <andreimpopescu@gmail.com> - 2019-07-10 05:40 +0200
    Re: fix for no ssh Gene Heskett <gheskett@shentel.net> - 2019-07-07 22:50 +0200

csiph-web