On Sun, 28 Sep 2025 07:26:20 -0400, Grimble <
grimble@nomail.afraid.org> wrote: <snip>
On a not-unrelated matter, I am logging many "IPv4: martian source
messages from 192.168.1 196 on dev enp5s0". Although ifcfg-enp5s0 has "BOOTPROTO=static,IPADDR=192.168.1.10", I can see from a network scan
that it has also picked up a DHCP address, which is the ...196 one. How
can I prevent that?
I get them too, but in my case I know it's due to having two nics (one wireless, and one wired),
with both working, when the ethernet is plugged into the laptop. I get maximum speed when
plugged in, but still remain connected when it's unplugged.
As long as it's working, I stopped worrying about martian packets a long time ago.
Assuming you're now using NetworkManager, as I am ...
[root@x9t ~]# grep -v ^'#' /etc/NetworkManager/NetworkManager.conf
[main]
plugins=ifcfg-rh,keyfile
dns=none
rc-manager=unmanaged
[root@x9t ~]# cat /etc/sysconfig/network-scripts/ifcfg-eth0
DEVICE=eth0
BOOTPROTO=static
IPADDR=192.168.10.222
NETMASK=255.255.0.0
GATEWAY=192.168.10.11
ONBOOT=yes
METRIC=5
MII_NOT_SUPPORTED=yes
USERCTL=yes
DNS1=127.0.0.1
DNS2=8.8.4.4
RESOLV_MODS=no
IPV6INIT=yes
IPV6TO4INIT=no
ACCOUNTING=no
NM_CONTROLLED=yes
# cat /etc/sysconfig/network-scripts/ifcfg-wlan0
DEVICE=wlan0
BOOTPROTO=static
IPADDR=192.168.10.22
NETMASK=255.255.255.0
GATEWAY=192.168.10.11
ONBOOT=yes
METRIC=35
MII_NOT_SUPPORTED=no
USERCTL=yes
DNS1=127.0.0.1
DNS2=8.8.8.8
RESOLV_MODS=no
WIRELESS_MODE=Managed
WIRELESS_ESSID=NOSSID
WIRELESS_ENC_KEY=s:munged
WIRELESS_WPA_DRIVER=wext
WIRELESS_WPA_REASSOCIATE=no
KEY_MGMT=WPA-PSK
WPA_PSK=munged
IPV6INIT=yes
IPV6TO4INIT=no
ACCOUNTING=no
NM_CONTROLLED=yes
The DNS= lines in the ifcfg- entries above are ignored due to the rc-manager=unmanaged.
I have the resolvconf package installed which sets the dns at boot
# cat /etc/resolvconf/resolv.conf.d/head
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN nameserver 127.0.0.1
nameserver ::1
nameserver 8.8.4.4
nameserver 8.8.8.8
Ignore the DO NOT EDIT comments in the above file. They are there so that they end up
in /etc/resolv.conf which is the file actually used to determine which name server to use.
[root@x9t ~]# cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN nameserver 127.0.0.1
nameserver ::1
nameserver 8.8.4.4
nameserver 8.8.8.8
[root@x9t ~]# journalctl -b --no-h|grep -i -e dhcp -e martian
Sep 28 11:34:10 NetworkManager[1779]: <info> [1759073650.0779] dhcp: init: Using DHCP client 'internal'
Sep 28 11:34:13 NetworkManager[1779]: <info> [1759073653.2761] dhcp6 (eth0): activation: beginning transaction (timeout in 45 seconds)
Sep 28 11:34:14 NetworkManager[1779]: <info> [1759073654.3023] dhcp6 (eth0): state changed new lease, address=2607:munged
Sep 28 11:34:16 kernel: IPv4: martian source 192.168.10.22 from 192.168.10.22, on dev eth0
Sep 28 11:34:17 NetworkManager[1779]: <info> [1759073657.0755] dhcp6 (wlan0): activation: beginning transaction (timeout in 45 seconds)
Sep 28 11:34:17 shorewall[5379]: Setting up Martian Logging...
Sep 28 11:34:18 NetworkManager[1779]: <info> [1759073658.1576] dhcp6 (wlan0): state changed new lease, address=2607:munged
Sep 28 11:34:18 kernel: IPv4: martian source 192.168.10.22 from 192.168.10.22, on dev eth0
Sep 28 11:34:20 kernel: IPv4: martian source 192.168.10.22 from 192.168.10.22, on dev eth0
I do get the martian packets as I have two nics both in use, but everything's working including
both ipv4 and ipv6, so I don't worry about the martians.
https://test-ipv6.com/ gives me 10/10
I have the bind name server installed and it's program named is running so the google
nameservers are not used (unless I stop the named process or it fails to start).
Regards, Dave Hodgins
--- MBSE BBS v1.1.1 (Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)