网络中大多数服务器上的火星源消息

Question

在Ubuntu 16.04和18.04服务器上，在/var/log/syslog文件中，通常有以下火星源消息：

Aug 23 06:42:51 scilit-solr kernel: [5417098.171549] IPv4: martian source 255.255.255.255 from 192.168.0.239, on dev bond0
Aug 23 06:42:51 scilit-solr kernel: [5417098.171565] ll header: 00000000: ff ff ff ff ff ff 00 8e f2 4e 0e 67 08 00        .........N.g..

如何找出谁试图在子网上进行通信？我试着逃跑

sudo tcpdump -i bond0 host 192.168.0.239

得到了这个：

06:46:41.750645 ARP, Request who-has 192.168.0.239 tell 192.168.0.239, length 46
06:46:41.750790 ARP, Request who-has 192.168.0.239 tell 192.168.0.239, length 46
06:46:41.754853 ARP, Request who-has 192.168.0.239 tell 192.168.0.239, length 46
06:46:41.754981 ARP, Request who-has 192.168.0.239 tell 192.168.0.239, length 46
06:46:41.759720 IP 192.168.0.239.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:8e:f2:4e:0e:67 (oui Unknown), length 253
06:46:41.759865 IP 192.168.0.239.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:8e:f2:4e:0e:67 (oui Unknown), length 253
06:46:46.081698 IP 192.168.0.239.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:8e:f2:4e:0e:67 (oui Unknown), length 253
06:46:46.081836 IP 192.168.0.239.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:8e:f2:4e:0e:67 (oui Unknown), length 253
06:46:52.414603 IP 192.168.0.239.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:8e:f2:4e:0e:67 (oui Unknown), length 253
06:46:52.414749 IP 192.168.0.239.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:8e:f2:4e:0e:67 (oui Unknown), length 253
06:47:03.750032 IP 192.168.0.239.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:8e:f2:4e:0e:67 (oui Unknown), length 253
06:47:03.750170 IP 192.168.0.239.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:8e:f2:4e:0e:67 (oui Unknown), length 253
06:47:26.089927 IP 192.168.0.239.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:8e:f2:4e:0e:67 (oui Unknown), length 253
06:47:26.090082 IP 192.168.0.239.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:8e:f2:4e:0e:67 (oui Unknown), length 253

目标将是确定谁经常发送的设备谁拥有和修复它的IP和子网。

Answer 1

虽然不是最好的方法，但结果是有的。

我更改了其中一个接口的IP地址，并首先尝试了SSH登录，但没有工作。然后尝试curl，并得到一个页面，这是我们的GS716Tv2交换机与它的默认配置的IP地址。我很快就会改变它，这个问题应该得到解决。