Mageia forum

Mageia 5.10.41-desktop-1.mga8

Hi all. I have been getting network errors for some time. These messages appear in logs as per below.
Can anyone offer an explanation? or more importantly suggest a solution to these/
I have tried to turn this network device off
sudo ip link set enp8s0 down
This has not been a permanent solution. Any help appreciated
++++++++++++++++++++++++++++++++++++++++++++
Network configuration is

Code: Select all

lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: enp6s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 00:24:8c:a7:d4:3b brd ff:ff:ff:ff:ff:ff
    inet 192.168.188.50/24 brd 192.168.188.255 scope global enp6s0
       valid_lft forever preferred_lft forever
    inet6 fe80::224:8cff:fea7:d43b/64 scope link
       valid_lft forever preferred_lft forever
3: enp8s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 00:23:cd:b1:63:26 brd ff:ff:ff:ff:ff:ff
    inet 192.168.188.21/24 brd 192.168.188.255 scope global enp8s0
       valid_lft forever preferred_lft forever
    inet6 fe80::223:cdff:feb1:6326/64 scope link
       valid_lft forever preferred_lft forever
4: br-3b7f2c0d74b8: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
    link/ether 02:42:0e:9c:17:cf brd ff:ff:ff:ff:ff:ff
    inet 172.18.0.1/16 brd 172.18.255.255 scope global br-3b7f2c0d74b8
       valid_lft forever preferred_lft forever
5: docker0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
    link/ether 02:42:3f:20:b6:2f brd ff:ff:ff:ff:ff:ff
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ snip

Problematic logs

Code: Select all

nel: IPv4: martian source 192.168.188.30 from 192.168.188.50, on dev enp8s0
Jan 27 11:30:14 Mageia kernel: ll header: 00000000: ff ff ff ff ff ff 00 24 8c a7 d4 3b 08 06
Jan 27 11:30:14 Mageia kernel: IPv4: martian source 192.168.188.33 from 192.168.188.50, on dev enp8s0
Jan 27 11:30:14 Mageia kernel: ll header: 00000000: ff ff ff ff ff ff 00 24 8c a7 d4 3b 08 06
Jan 27 11:30:15 Mageia kernel: IPv4: martian source 192.168.188.33 from 192.168.188.50, on dev enp8s0
Jan 27 11:30:15 Mageia kernel: ll header: 00000000: ff ff ff ff ff ff 00 24 8c a7 d4 3b 08 06
Jan 27 11:30:15 Mageia kernel: IPv4: martian source 192.168.188.30 from 192.168.188.50, on dev enp8s0
Jan 27 11:30:15 Mageia kernel: ll header: 00000000: ff ff ff ff ff ff 00 24 8c a7 d4 3b 08 06
Jan 27 11:30:15 Mageia kernel: IPv4: martian source 192.168.188.37 from 192.168.188.50, on dev enp8s0


Also this.

Code: Select all

Jan 27 11:31:21 Mageia kernel: ll header: 00000000: ff ff ff ff ff ff 00 24 8c a7 d4 3b 08 06
Jan 27 11:31:22 Mageia kernel: IPv4: martian source 192.168.188.24 from 192.168.188.50, on dev enp8s0
Jan 27 11:31:22 Mageia kernel: ll header: 00000000: ff ff ff ff ff ff 00 24 8c a7 d4 3b 08 06
Jan 27 11:31:23 Mageia kernel: IPv4: martian source 192.168.188.24 from 192.168.188.50, on dev enp8s0

You need to check your network and network settings. There is a vast amount of information regarding this topic available.
https://www.thegeekdiary.com/how-to-int ... sages/amp/
https://www.suse.com/support/kb/doc/?id=000016540
...

Additionally you should immediatly update your system as you are using a heavily outdated kernel from May 2021!.

Any idea how to permanently disable enp8s0?

Thanks for noting the kernel problem. The system is being updated however it may not be booting into the new kernel. Something else to look at.

Thanks

brm wrote:Any idea how to permanently disable enp8s0?

Depends what you are using to manage your connections, either drakconnect or networkmanager or ... ?

Although it would be interesting why you have to network interfaces with an IP from the same subnet, usually that doesn't make much sense.

Note - Desktop PC here.
Looking past the spider webs and dust I started checking network connections to the PC. One cable was coming from an old PCI network card. This ended at a network switch used to create more network connections for several Single Board Computers.
Was this necessary? Was it still in use? I have disconnected this and trust that the martian source errors have ceased.

Thanks for your suggestions.

Please don't forget to mark the thread as solved, by editing the subject of the first post and prefix it with [SOLVED], thanks in advance.