Dev1 Galaxy Forum / [SOLVED] Devuan 6 excalibur, OpenRC, networking, /etc/hosts ingnored

Re: [SOLVED] Devuan 6 excalibur, OpenRC, networking, /etc/hosts ingnored

dummy@example.com (Andre4freedom) — Thu, 14 Aug 2025 16:14:17 +0000

@steve_v
thank you very much, steve_v... you are that bright spark to bring light into this mystery.
It's entirely my fault that I recorded the IP address wrongly - I didn't know that.

I've corrected the hosts entry and everything works fine as it should.
I don't know which devil has bitten me to add a leading 0 in an octet.

BTW: I never spat upon NetworkManager. I only tried to understand the problem. Thank you.

Re: [SOLVED] Devuan 6 excalibur, OpenRC, networking, /etc/hosts ingnored

dummy@example.com (steve_v) — Thu, 14 Aug 2025 13:16:53 +0000

Well for one,

172.22.22.05	colossus.home colossus

"172.22.22.05" isn't a correctly formatted IP address...
And for two,

getent hosts

would have made it fairly obvious whether or not your /etc/hosts file was the problem, since it returns only valid entries.

$ printf '%s\n' "* File:"; cat /etc/hosts; printf '%s\n' "* Reality:"; getent hosts
* File:
127.0.0.1 localhost damnation.lan damnation

# The following lines are desirable for IPv6 capable hosts
::1     ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
172.22.22.05    colossus.home colossus

* Reality:
127.0.0.1       localhost damnation.lan damnation
127.0.0.1       ip6-localhost ip6-loopback

$ printf '%s\n' "* File:"; cat /etc/hosts; printf '%s\n' "* Reality:"; getent hosts
* File:
127.0.0.1 localhost damnation.lan damnation

# The following lines are desirable for IPv6 capable hosts
::1     ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
172.22.22.5     colossus.home colossus

* Reality:
127.0.0.1       localhost damnation.lan damnation
127.0.0.1       ip6-localhost ip6-loopback
172.22.22.5     colossus.home colossus

As I said, networkmangler is a red herring and it was only brought up because everyone here loves to hate on it.
I mean I kinda hate it too, but going straight to "Damn new software, the old ways were better, life was simpler, bloody clouds etc. etc." before even trying to investigate the problem is plain ridiculous.

Re: [SOLVED] Devuan 6 excalibur, OpenRC, networking, /etc/hosts ingnored

dummy@example.com (Andre4freedom) — Wed, 13 Aug 2025 18:13:12 +0000

Thank you for your hints.
I will pause it here. Once a bright idea comes up, I will try again and let you know.
BTW: the /etc/resolv.conf is not the problem. Name-resolution is working except for the /etc/hosts lookup.
(only local fixed addresses are in there.)

Re: [SOLVED] Devuan 6 excalibur, OpenRC, networking, /etc/hosts ingnored

dummy@example.com (g4sra) — Wed, 13 Aug 2025 16:59:54 +0000

Andre4freedom, can you describe what did\didn't happen ...

Re: [SOLVED] Devuan 6 excalibur, OpenRC, networking, /etc/hosts ingnored

dummy@example.com (rolfie) — Wed, 13 Aug 2025 16:37:46 +0000

I have seen something in a German portal that you can configure NM to leave the resolv.conf alone.

Re: [SOLVED] Devuan 6 excalibur, OpenRC, networking, /etc/hosts ingnored

dummy@example.com (Andre4freedom) — Wed, 13 Aug 2025 16:22:18 +0000

surprise surprise....
Artix (OpenRC, Cinnamon) shows the same problem

Artix (OpenRC, XFCE) does not.

Artix with Cinnamon uses NetworkManager
Artrix with XFCE uses Connman.

Older versions (older Cinnamon and older nm) worked correctly.

Linux Mint did work, but I have not tested the latest version.

Scratching my head... the devil must be hidden somewhere.

Re: [SOLVED] Devuan 6 excalibur, OpenRC, networking, /etc/hosts ingnored

dummy@example.com (Andre4freedom) — Wed, 13 Aug 2025 14:55:26 +0000

@steve_v
here you are a little bit off the problem.
The /etc/resolv.conf is always correct, after every reboot too.
All files, /etc/hosts, /etc/nsswitch.conf are correct.

The ISP box is correctly set up and gives the correct name-server addresses.

I can connect to every Internet-resource without problems.
mDNS resources are found as well.
Only that bloody host-entry "172.22.22.05 colossus.home colossus" in /etc/hosts is ignored.
I have tested with former Devuan releases: no problem
I have tested Artix: no problem
I have tested Linux Mint: no problem.

Next thing I try is to replace network-manager with connman. That's how it works in Artix.
I will keep you posted, be patient, I'm busy.

But anyway, steve_v, thank you for your good intentions.

Re: [SOLVED] Devuan 6 excalibur, OpenRC, networking, /etc/hosts ingnored

dummy@example.com (steve_v) — Wed, 13 Aug 2025 11:32:19 +0000

Altoid wrote:

got tired of seeing my /etc/resolv.conf continually being tampered with...
disabled the crap Network Manager...
whose bloody $%& workstation is it?

rolfie wrote:

NetworkManager WILL affect the /etc/resolv.conf and take it out of the loop. Thats why I omit using NetworkManager

FFS people, get a grip. Networkmangler will mangle /etc/resolv.conf if it is configured to do so. You can shout about it, you can remove it... Or you could just do a 10 second search and set it up to do what you want.

Andre4freedom wrote:

remove the network manager. That's okay for a workstation PC, but NOT for a laptop.

Indeed. While there are many other ways to configure networking on a mobile device, networkmangler + modemmangler + [all the 50 plugins] does make a certain amount of sense.
Unfortunately, the prevailing attitude here seems to be shouting "[x] is crap, I hate [x], why does this new complicated [x] exist" rather than addressing the question in a sensible manner.

Re: [SOLVED] Devuan 6 excalibur, OpenRC, networking, /etc/hosts ingnored

dummy@example.com (Andre4freedom) — Wed, 13 Aug 2025 09:30:34 +0000

@rolfie
I see the discrepancy, and I agree with you.
And, the /etc/resolv.conf is not even the problem here.
The /etc/nsswitch.conf is correct too: it states for hosts lookup it should consult the files first (/etc/hosts) and then mdsn and then dns.
That's the point. In that case names in the /etc/hosts file must be resolved as it always did. It does not now.

I see the ultimate outcome..... to remove the network manager. That's okay for a workstation PC, but NOT for a laptop. I fear to have to test a laptop for that reason.
I still wonder if the kernel may be to blame - it goes beyond my understanding.

Re: [SOLVED] Devuan 6 excalibur, OpenRC, networking, /etc/hosts ingnored

dummy@example.com (rolfie) — Wed, 13 Aug 2025 08:38:01 +0000

NetworkManager shouldn't affect /etc/resolv.conf, /etc/hosts or any of these files, except, unfortunately, the /etc/resolv.conf file.

Please read again, you see the discrepancy?

NetworkManager WILL affect the /etc/resolv.conf and take it out of the loop. Thats why I omit using NetworkManager on my workstation. On my small home network I am using static addressing.

Re: [SOLVED] Devuan 6 excalibur, OpenRC, networking, /etc/hosts ingnored

dummy@example.com (Andre4freedom) — Wed, 13 Aug 2025 07:15:45 +0000

Oh, it looks like the kernel version is important:

root@tinkerbox:~# lsb_release -a
No LSB modules are available.
Distributor ID:	Devuan
Description:	Devuan GNU/Linux 6 (excalibur/ceres)
Release:	6
Codename:	excalibur ceres
root@tinkerbox:~# 

root@tinkerbox:~# uname -a
Linux tinkerbox 6.12.38+deb13-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.12.38-1 (2025-07-16) x86_64 GNU/Linux
root@tinkerbox:~#

And the rest of all information in one block:

root@tinkerbox:~# ifconfig
eth0: flags=4163  mtu 1500
        inet 172.22.22.60  netmask 255.255.255.0  broadcast 172.22.22.255
        inet6 fe80::c42c:d3ce:d1e1:f30f  prefixlen 64  scopeid 0x20
        ether 70:54:d2:ab:5e:4e  txqueuelen 1000  (Ethernet)
        RX packets 179  bytes 109589 (107.0 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 215  bytes 25830 (25.2 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 20  memory 0xf7e00000-f7e20000  

eth1: flags=4099  mtu 1500
        ether 70:54:d2:ab:5e:4f  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 18  memory 0xf7d00000-f7d20000  

lo: flags=73  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 31  bytes 4263 (4.1 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 31  bytes 4263 (4.1 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

root@tinkerbox:~# netstat -r
Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
default         172.22.22.1     0.0.0.0         UG        0 0          0 eth0
172.22.22.0     0.0.0.0         255.255.255.0   U         0 0          0 eth0

root@tinkerbox:~# hostname
tinkerbox

root@tinkerbox:~# cat /etc/networks
default		0.0.0.0
loopback	127.0.0.0
link-local	169.254.0.0

root@tinkerbox:~# cat /etc/resolv.conf 
# Generated by NetworkManager
nameserver 213.221.144.240
nameserver 213.221.143.240

***********************************

root@tinkerbox:~# ping www.google.com
PING www.google.com (142.250.178.196) 56(84) bytes of data.
64 bytes from pnzrha-aj-in-f4.1e100.net (142.250.178.196): icmp_seq=1 ttl=116 time=22.8 ms
64 bytes from pnzrha-aj-in-f4.1e100.net (142.250.178.196): icmp_seq=2 ttl=116 time=25.9 ms

root@tinkerbox:~# ping colossus
ping: colossus: Name or service not known
root@tinkerbox:~# ping colossus.home
ping: colossus.home: Name or service not known
root@tinkerbox:~# ping printer.home
ping: printer.home: Name or service not known

root@tinkerbox:~# ping printer
PING printer (172.22.22.12) 56(84) bytes of data.
64 bytes from printer (172.22.22.12): icmp_seq=1 ttl=255 time=0.637 ms
64 bytes from printer (172.22.22.12): icmp_seq=2 ttl=255 time=0.650 ms
64 bytes from printer (172.22.22.12): icmp_seq=3 ttl=255 time=0.646 ms
64 bytes from printer (172.22.22.12): icmp_seq=4 ttl=255 time=0.638 ms
// what a surprise! The printer gets resolved by mDNS //

***********************************

# /etc/nsswitch.conf
#
# Example configuration of GNU Name Service Switch functionality.
# If you have the `glibc-doc-reference' and `info' packages installed, try:
# `info libc "Name Service Switch"' for information about this file.

passwd:         files
group:          files
shadow:         files
gshadow:        files

hosts:          files mdns4_minimal [NOTFOUND=return] dns
networks:       files

protocols:      db files
services:       db files
ethers:         db files
rpc:            db files

netgroup:       nis
root@tinkerbox:~#

Re: [SOLVED] Devuan 6 excalibur, OpenRC, networking, /etc/hosts ingnored

dummy@example.com (Andre4freedom) — Wed, 13 Aug 2025 07:02:50 +0000

Thank you for your responses and questions.

@g4sra

root@tinkerbox:~# cat /etc/hosts
127.0.0.1	localhost
127.0.1.1	tinkerbox.home	tinkerbox

172.22.22.05	colossus.home colossus
172.22.22.12	printer

I only added the last 2 lines.

@Altoid
Yes, it's quite possible it will come to that, but: NetworkManager shouldn't affect /etc/resolv.conf, /etc/hosts or any of these files, except, unfortunately, the /etc/resolv.conf file.

@both
Would you like to get all network information? I could put it in an extra response.
Again, that problem never appeared in previous releases.

Re: [SOLVED] Devuan 6 excalibur, OpenRC, networking, /etc/hosts ingnored

dummy@example.com (Altoid) — Tue, 12 Aug 2025 20:09:36 +0000

Hello:

Andre4freedom wrote:

... NetworkManager is always installed ...

Yes, that it is.

I eventually got tired of seeing my /etc/resolv.conf continually being tampered with.
Because, after all ... Just whose bloody $%& workstation is it?

Good old WiCD did not do that.
But, alas, it is no longer available.

So I just disabled the crap Network Manager and that was it.

My ethernet link comes up at boot and I just use ifdown / ifup when I want to do otherwise or connect to a friendly neighbour's AP if my fibre-link provider finds the opportunity to screw up something.

Doing that has made life much simpler.
As always, YMMV.

Best,

Re: [SOLVED] Devuan 6 excalibur, OpenRC, networking, /etc/hosts ingnored

dummy@example.com (g4sra) — Tue, 12 Aug 2025 18:31:44 +0000

Andre4freedom, can you post what you changed in /etc/hosts and describe what did\didnt happen.
Once I know that I can test my install to see if it is affected.

[SOLVED] Devuan 6 excalibur, OpenRC, networking, /etc/hosts ingnored

dummy@example.com (Andre4freedom) — Tue, 12 Aug 2025 15:21:06 +0000

Hello,
testing the latest iso, devuan-excalibur_6.0-20250809_amd64_netinstall.iso,
I ran into a problem:
The file /etc/hosts is simply ignored.
This happened while testing both DEs: XFCE4 and Cinnamon.
It is a standard installation with no tinkering. Standard Linux-utilities and ssh-server always selected too.

The problem did not show up when testing the previous pre-releases, and never showed up with any former Devuan release (3,4,5).
The problems doesn't manifest when testing Artix-OpenRC-XFCE.

I just edit the /etc/hosts file to test.
/etc/resolv.conf and other networking details are all correct by default.
Internet access and even CUPS-driverless-printing works correctly.
Strange.

I know that NetworkManager is always installed by default.
Has anyone encountered that bug as well?