| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 27 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 40:23:31 |
| Calls: | 631 |
| Calls today: | 2 |
| Files: | 1,187 |
| D/L today: |
24 files (29,813K bytes) |
| Messages: | 174,391 |
I've replaced the motherboard on this machine. Most things worked on start-up, but there's a problem with ethernet connections. Before the
change, the ethernet connection was enp2s0, statically linked to
192.168.1.9.
Now ip addr tells me the connection is enp4s0, dynamically linked to 192.168.1.188. When I try to reconfigure it to static/192.168.1.9, I'm
told that "that address is already used by a connection that starts on
boot (enp2s0) and that I have to configure it not to start at boot."
I don't understand where enp2s0 is declared, because ip adsdr makes no mention.
Help!
I've replaced the motherboard on this machine. Most things worked on start-up, but there's a problem with ethernet connections. Before the change, the ethernet connection was enp2s0, statically linked to 192.168.1.9.
Now-a ip addr tells me the connection is enp4s0, dynamically linked to 192.168.1.188. When I try to reconfigure it to static/192.168.1.9, I'm
told that "that address is already used by a connection that starts on
boot (enp2s0) and that I have to configure it not to start at boot."
I don't understand where enp2s0 is declared, because ip adsdr makes no mention.
Help!
On Tue, 02 Sep 2025 08:27:58 -0400, Grimble <grimble@nomail.afraid.org> wrote:Thanks, David, that did it.
I've replaced the motherboard on this machine. Most things worked on
start-up, but there's a problem with ethernet connections. Before the
change, the ethernet connection was enp2s0, statically linked to
192.168.1.9.
Now-a ip addr tells me the connection is enp4s0, dynamically linked to
192.168.1.188. When I try to reconfigure it to static/192.168.1.9, I'm
told that "that address is already used by a connection that starts on
boot (enp2s0) and that I have to configure it not to start at boot."
I don't understand where enp2s0 is declared, because ip adsdr makes no
mention.
Help!
The old one is still referred to in a file /etc/sysconfig/network- scripts/ifcfg-enp2s0 that
was created when that nic existed.
Either delete the file from that directory manually, or you can delete
it using draknetcenter.
Instead of deleting it though, you may want to move it to /root so you
can check it's values later.
Regards, Dave Hodgins
On Tue, 02 Sep 2025 08:27:58 -0400, Grimble <grimble@nomail.afraid.org> wrote:
The old one is still referred to in a file /etc/sysconfig/network- scripts/ifcfg-enp2s0 thatOn a not-unrelated matter, I am logging many "IPv4: martian source
was created when that nic existed.
Either delete the file from that directory manually, or you can delete
it using draknetcenter.
Instead of deleting it though, you may want to move it to /root so you
can check it's values later.
Regards, Dave Hodgins
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?
On Sun, 28 Sep 2025 07:26:20 -0400, Grimble <grimble@nomail.afraid.org> wrote:Thanks Dave. I wasn't worried about the martians per se, because
<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-a ...
[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)
#-a-a-a-a 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)
#-a-a-a-a 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>-a [1759073650.0779] dhcp:
init: Using DHCP client 'internal'
Sep 28 11:34:13 NetworkManager[1779]: <info>-a [1759073653.2761] dhcp6 (eth0): activation: beginning transaction (timeout in 45 seconds)
Sep 28 11:34:14 NetworkManager[1779]: <info>-a [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>-a [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>-a [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