Re: Debugging what is deleting/recreating /etc/resolv.conf with wrong configuration, on debian stable

From	davenull@tuxfamily.org
Newsgroups	linux.debian.user
Subject	Re: Debugging what is deleting/recreating /etc/resolv.conf with wrong configuration, on debian stable
Date	2023-02-28 16:10 +0100
Message-ID	<G49M5-972L-1@gated-at.bofh.it> (permalink)
References	<G20WC-7JT0-5@gated-at.bofh.it> <G28AN-7OAd-1@gated-at.bofh.it> <G29nb-7P6r-1@gated-at.bofh.it> <G2h1n-7Ufo-3@gated-at.bofh.it> <G3ZMJ-90Ch-1@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

On 2023-02-28 05:27, David Wright wrote:
> On Thu 23 Feb 2023 at 11:23:30 (+0100), davenull@tuxfamily.org wrote:
>> On 2023-02-23 02:59, conover@panix.com wrote:
>> 
>> […]
>> 
>> On the newer work laptop on the other hand, there is that eth0 block,
>> there's is no eth0 interface on my system (there's enp.* and enx.*
>> systemd names, instead)
>> BUT I never had the slow/timeout-waiting boot process unlike the
>> personal was reinstall from zero instead of upgraded years ago only to
>> change HDD to SSD, and to change partitioning to encrypted LVM.
> 
> What are these enp… (waste of time hiding that name) and enx…
> interfaces (and any others), and what are they used for.
> 

It's the systemd-style so-called "predictable" interfaces names.
Replacing the older the eth0, wlan0, and so on…

ens-something (annoying name made of multiple letters and digits) is the 
new name for eth0
wlx-something or wlp-something for wlan0
enx-insert-long-hexadecimal-number-here is well… I have no damn idea.

Seen this last one only my work's computer, not personal one. Much 
newer, maybe have some optional network hardware?
Not sure, but it's not virtual interface for the VPN. which is still 
named tun0 as it used to be before systemd.
And the unknown interface is still around even without the VPN process 
running

And it's not really hiding. it's just a name I can never fully remember
and didn't bother to check full name. It doesn't really matter.
What matters is the interface is not called eth0 anymore, but is
instead called ens-whatever-thefullname-is. And the interface name used 
in
/etc/network/interfaces.d/setup refers to a network interface which 
doen't exist anymore

Yet it does NOT break the network, that why I think something else 
replaced.
Otherwise, I fail to see how it would work while referencing to the 
wrong interface name.

(Also, the new name for wlan0 interface is "wlx" followed by an UID *on 
some* systems. not all
So it actually does make sense to hide it, for such systems)

>> So my guess is /etc/network/interface.* has been replaced with
>> something also. Since it refers to non-exitent interfaces names
>> without breaking the network or slowing down the boot process.
>> 
>> Also, the switching to systemd styles interfaces names has been
>> following by a weird behaviour on my personal computer. It has a
>> "failed" error message at startup, for the network (or is networking?
>> it never remember the correct name) service, without breaking the
>> network… it weirdly just works. I never figured out what replaces that
>> service. If anyone has any idea?
> 
> Different installation scripts and/or individual sysadmins can place
> files with a variety of names in /etc/network/interface.d/. So their
> removal can be rather sporadic: Debian won't know their names, and
> deinstallation scripts might leave them, if they get run at all.
> 
> It's worrying that such files are there if they have the wrong
> interface names in them. It might suggest ancient cruft or, just
> as easily, network installation scripts that are broken, or designed
> for a different system/distribution.
> 
> What's the output from   ls -lR /etc/network* /etc/systemd/network*

Here's the output.

---

ls -lR /etc/network* /etc/systemd/network*
-rw-r--r-- 1 root root   60  9 oct.   2021 /etc/networks
-rw-r--r-- 1 root root  609  2 févr.  2021 /etc/systemd/networkd.conf

/etc/network:
total 24
drwxr-xr-x 2 root root 4096 21 févr. 15:52 if-down.d
drwxr-xr-x 2 root root 4096  2 déc.   2021 if-post-down.d
drwxr-xr-x 2 root root 4096  2 déc.   2021 if-pre-up.d
drwxr-xr-x 2 root root 4096 21 févr. 15:52 if-up.d
-rw-r--r-- 1 root root  321  2 déc.   2021 interfaces
drwxr-xr-x 2 root root 4096  2 déc.   2021 interfaces.d

/etc/network/if-down.d:
total 8
-rwxr-xr-x 1 root root 1015  6 févr.  2021 avahi-autoipd
-rwxr-xr-x 1 root root 1677 13 janv.  2022 clamav-freshclam-ifupdown
lrwxrwxrwx 1 root root   32  2 déc.   2021 wpasupplicant -> 
../../wpa_supplicant/ifupdown.sh

/etc/network/if-post-down.d:
total 4
-rwxr-xr-x 1 root root 1409  7 mars   2020 wireless-tools
lrwxrwxrwx 1 root root   32  2 déc.   2021 wpasupplicant -> 
../../wpa_supplicant/ifupdown.sh

/etc/network/if-pre-up.d:
total 12
-rwxr-xr-x 1 root root  344 30 juin   2016 ethtool
-rwxr-xr-x 1 root root 4191  7 mars   2020 wireless-tools
lrwxrwxrwx 1 root root   32  2 déc.   2021 wpasupplicant -> 
../../wpa_supplicant/ifupdown.sh

/etc/network/if-up.d:
total 12
-rwxr-xr-x 1 root root  923  6 févr.  2021 avahi-autoipd
-rwxr-xr-x 1 root root 1677 13 janv.  2022 clamav-freshclam-ifupdown
-rwxr-xr-x 1 root root 1685 30 juin   2016 ethtool
lrwxrwxrwx 1 root root   32  2 déc.   2021 wpasupplicant -> 
../../wpa_supplicant/ifupdown.sh

/etc/network/interfaces.d:
total 4
-rw-r--r-- 1 root root 63  9 oct.   2021 setup

/etc/systemd/network:
total 0

---

Not sue if it contains anything DHCP client related
Beside the /etc/network/interfaces.d/setup which contains only local 
interface and eth0
But again. I don't to fully stop using DHCP, which is would be the most 
obvious thing I could do on the setup file if it were used.

I just don't want the DHCP client send requests to my home's network 
instead of sending requests through the VPN route
so the workplace's DHCP sees and answers to the requests, instead of 
home router answering to these requests

I fail to see why the DHCP client would send it requests to 192.168.1.1 
(my home's gateway) instead of using the VPN interface/route/whatever.
dhclient must have some wrong conf, but I never changed the default 
conf, So I have no idea what part may be wrong or what's missing

> 
> Cheers,
> David.

Thread

Debugging what is deleting/recreating /etc/resolv.conf with wrong  configuration, on debian stable davenull@tuxfamily.org - 2023-02-22 18:20 +0100
  Re: Debugging what is deleting/recreating /etc/resolv.conf with  wrong configuration, on debian stable Roberto C. Sánchez <roberto@debian.org> - 2023-02-22 18:30 +0100
  Re: Debugging what is deleting/recreating /etc/resolv.conf with  wrong configuration, on debian stable Christoph Brinkhaus <c.brinkhaus@t-online.de> - 2023-02-22 18:40 +0100
    Re: Debugging what is deleting/recreating /etc/resolv.conf with wrong  configuration, on debian stable davenull@tuxfamily.org - 2023-02-23 11:40 +0100
      Re: Debugging what is deleting/recreating /etc/resolv.conf with  wrong configuration, on debian stable Reco <recoverym4n@enotuniq.net> - 2023-02-23 18:20 +0100
  Re: Debugging what is deleting/recreating /etc/resolv.conf with  wrong configuration, on debian stable Greg Wooledge <greg@wooledge.org> - 2023-02-22 19:30 +0100
  Re: Debugging what is deleting/recreating /etc/resolv.conf with  wrong configuration, on debian stable David Wright <deblis@lionunicorn.co.uk> - 2023-02-22 22:10 +0100
    Re: Debugging what is deleting/recreating /etc/resolv.conf with wrong  configuration, on debian stable davenull@tuxfamily.org - 2023-02-23 10:50 +0100
      Re: Debugging what is deleting/recreating /etc/resolv.conf with  wrong configuration, on debian stable <tomas@tuxteam.de> - 2023-02-23 11:00 +0100
        Re: Debugging what is deleting/recreating /etc/resolv.conf with wrong  configuration, on debian stable davenull@tuxfamily.org - 2023-02-23 11:40 +0100
      Re: Debugging what is deleting/recreating /etc/resolv.conf with  wrong configuration, on debian stable David Wright <deblis@lionunicorn.co.uk> - 2023-02-24 06:40 +0100
        Re: Debugging what is deleting/recreating /etc/resolv.conf with  wrong configuration, on debian stable <tomas@tuxteam.de> - 2023-02-24 06:50 +0100
        Re: Debugging what is deleting/recreating /etc/resolv.conf with wrong  configuration, on debian stable davenull@tuxfamily.org - 2023-02-24 10:30 +0100
          Re: Debugging what is deleting/recreating /etc/resolv.conf with  wrong configuration, on debian stable <tomas@tuxteam.de> - 2023-02-24 10:30 +0100
            Re: Debugging what is deleting/recreating /etc/resolv.conf with wrong  configuration, on debian stable davenull@tuxfamily.org - 2023-02-24 11:30 +0100
              Re: Debugging what is deleting/recreating /etc/resolv.conf with  wrong configuration, on debian stable tomas@tuxteam.de - 2023-02-24 11:50 +0100
              Re: Debugging what is deleting/recreating /etc/resolv.conf with wrong  configuration, on debian stable davenull@tuxfamily.org - 2023-02-27 15:20 +0100
                Re: Debugging what is deleting/recreating /etc/resolv.conf with  wrong configuration, on debian stable Greg Wooledge <greg@wooledge.org> - 2023-02-27 15:40 +0100
          Re: Debugging what is deleting/recreating /etc/resolv.conf with  wrong configuration, on debian stable Greg Wooledge <greg@wooledge.org> - 2023-02-24 13:30 +0100
          Re: Debugging what is deleting/recreating /etc/resolv.conf with  wrong configuration, on debian stable David Wright <deblis@lionunicorn.co.uk> - 2023-02-25 01:30 +0100
          Forcing dhclient to not ignore tun0 interface when it's available davenull@tuxfamily.org - 2023-03-02 11:50 +0100
            Re: Forcing dhclient to not ignore tun0 interface when it's  available Tim Woodall <debianuser@woodall.me.uk> - 2023-03-03 04:10 +0100
              Re: Forcing dhclient to not ignore tun0 interface when it's available Max Nikulin <manikulin@gmail.com> - 2023-03-03 06:30 +0100
                Re: Forcing dhclient to not ignore tun0 interface when it's  available Tim Woodall <debianuser@woodall.me.uk> - 2023-03-03 07:40 +0100
                Re: Forcing dhclient to not ignore tun0 interface when it's available Max Nikulin <manikulin@gmail.com> - 2023-03-03 16:10 +0100
                Re: Forcing dhclient to not ignore tun0 interface when it's available David Wright <deblis@lionunicorn.co.uk> - 2023-03-03 16:20 +0100
                Re: Forcing dhclient to not ignore tun0 interface when it's available davenull@tuxfamily.org - 2023-03-06 13:40 +0100
                Re: Forcing dhclient to not ignore tun0 interface when it's available David Wright <deblis@lionunicorn.co.uk> - 2023-03-07 05:10 +0100
                Re: Forcing dhclient to not ignore tun0 interface when it's available davenull@tuxfamily.org - 2023-03-07 17:20 +0100
                Re: Forcing dhclient to not ignore tun0 interface when it's available David Wright <deblis@lionunicorn.co.uk> - 2023-03-10 02:00 +0100
                Re: Forcing dhclient to not ignore tun0 interface when it's available davenull@tuxfamily.org - 2023-03-06 13:20 +0100
                Re: Forcing dhclient to not ignore tun0 interface when it's available David Wright <deblis@lionunicorn.co.uk> - 2023-03-07 05:10 +0100
                Re: Forcing dhclient to not ignore tun0 interface when it's available davenull@tuxfamily.org - 2023-03-07 17:00 +0100
                Re: Forcing dhclient to not ignore tun0 interface when it's available Max Nikulin <manikulin@gmail.com> - 2023-03-07 16:30 +0100
                Re: Forcing dhclient to not ignore tun0 interface when it's available davenull@tuxfamily.org - 2023-03-07 18:00 +0100
                Re: Forcing dhclient to not ignore tun0 interface when it's available David Wright <deblis@lionunicorn.co.uk> - 2023-03-10 02:00 +0100
                Re: Forcing dhclient to not ignore tun0 interface when it's available davenull@tuxfamily.org - 2023-03-10 09:50 +0100
            Re: Forcing dhclient to not ignore tun0 interface when it's available David Wright <deblis@lionunicorn.co.uk> - 2023-03-03 06:30 +0100
              Re: Forcing dhclient to not ignore tun0 interface when it's available davenull@tuxfamily.org - 2023-03-03 18:10 +0100
                Re: Forcing dhclient to not ignore tun0 interface when it's available David Wright <deblis@lionunicorn.co.uk> - 2023-03-04 18:40 +0100
  Re: Debugging what is deleting/recreating /etc/resolv.conf with wrong  configuration, on debian stable Cindy Sue Causey <butterflybytes@gmail.com> - 2023-02-23 02:30 +0100
    Re: Debugging what is deleting/recreating /etc/resolv.conf with wrong configuration, on debian stable conover@panix.com (John Conover) - 2023-02-23 03:20 +0100
      Re: Debugging what is deleting/recreating /etc/resolv.conf with wrong  configuration, on debian stable davenull@tuxfamily.org - 2023-02-23 11:30 +0100
        Re: Debugging what is deleting/recreating /etc/resolv.conf with wrong  configuration, on debian stable Jeremy Ardley <jeremy@ardley.org> - 2023-02-23 11:40 +0100
        Re: Debugging what is deleting/recreating /etc/resolv.conf with  wrong configuration, on debian stable David Wright <deblis@lionunicorn.co.uk> - 2023-02-28 05:30 +0100
          Re: Debugging what is deleting/recreating /etc/resolv.conf with wrong  configuration, on debian stable davenull@tuxfamily.org - 2023-02-28 16:10 +0100
            Re: Debugging what is deleting/recreating /etc/resolv.conf with  wrong configuration, on debian stable Tixy <tixy@yxit.co.uk> - 2023-02-28 17:00 +0100
            Re: Debugging what is deleting/recreating /etc/resolv.conf with  wrong configuration, on debian stable David Wright <deblis@lionunicorn.co.uk> - 2023-03-02 00:30 +0100
              Re: Debugging what is deleting/recreating /etc/resolv.conf with wrong  configuration, on debian stable davenull@tuxfamily.org - 2023-03-02 10:40 +0100
                Re: Debugging what is deleting/recreating /etc/resolv.conf with  wrong configuration, on debian stable Greg Wooledge <greg@wooledge.org> - 2023-03-02 13:40 +0100
                Re: Debugging what is deleting/recreating /etc/resolv.conf with wrong  configuration, on debian stable davenull@tuxfamily.org - 2023-03-02 13:50 +0100
                Re: Debugging what is deleting/recreating /etc/resolv.conf with wrong  configuration, on debian stable davenull@tuxfamily.org - 2023-03-02 14:10 +0100
                Re: Debugging what is deleting/recreating /etc/resolv.conf with  wrong configuration, on debian stable Greg Wooledge <greg@wooledge.org> - 2023-03-02 14:20 +0100
                Re: Debugging what is deleting/recreating /etc/resolv.conf with wrong  configuration, on debian stable davenull@tuxfamily.org - 2023-03-02 16:20 +0100
                Re: Debugging what is deleting/recreating /etc/resolv.conf with wrong  configuration, on debian stable David <bouncingcats@gmail.com> - 2023-03-02 16:40 +0100
                Re: Debugging what is deleting/recreating /etc/resolv.conf with wrong  configuration, on debian stable David <bouncingcats@gmail.com> - 2023-03-02 16:20 +0100
                Re: Debugging what is deleting/recreating /etc/resolv.conf with  wrong configuration, on debian stable Curt <curty@free.fr> - 2023-03-02 18:30 +0100
                Re: Debugging what is deleting/recreating /etc/resolv.conf with  wrong configuration, on debian stable David Wright <deblis@lionunicorn.co.uk> - 2023-03-02 19:20 +0100
                Re: Debugging what is deleting/recreating /etc/resolv.conf with  wrong configuration, on debian stable <tomas@tuxteam.de> - 2023-03-02 20:30 +0100
                Re: Debugging what is deleting/recreating /etc/resolv.conf with  wrong configuration, on debian stable David Wright <deblis@lionunicorn.co.uk> - 2023-03-03 06:20 +0100

csiph-web