systemd-journalctl -f and to many error records..;(

English Network/Internet
#1

Leap 42.1

Why i see to many records ?

# systemd-journalctl -f
-- Logs begin at Fri 2016-03-04 05:41:30 MSK. --
Mar 11 20:48:43 mylinuxkap.suse kernel: IPv4: martian destination 0.0.0.0 from 169.254.54.119, dev eth0
Mar 11 20:48:44 mylinuxkap.suse kernel: IPv4: martian destination 0.0.0.0 from 169.254.54.119, dev eth0
Mar 11 20:48:45 mylinuxkap.suse kernel: IPv4: martian destination 0.0.0.0 from 169.254.54.119, dev eth0
Mar 11 20:48:46 mylinuxkap.suse kernel: IPv4: martian destination 0.0.0.0 from 169.254.54.119, dev eth0
Mar 11 20:48:47 mylinuxkap.suse kernel: IPv4: martian destination 0.0.0.0 from 169.254.54.119, dev eth0
Mar 11 20:48:48 mylinuxkap.suse kernel: IPv4: martian destination 0.0.0.0 from 169.254.54.119, dev eth0


# ifconfig 
eth0      Link encap:Ethernet  HWaddr 00:17:A4:D3:7C:BD  
          inet addr:10.2.96.140  Bcast:10.2.96.255  Mask:255.255.255.0
          inet6 addr: fe80::217:a4ff:fed3:7cbd/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:15076068 errors:0 dropped:46 overruns:0 frame:0
          TX packets:7652584 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:16527078117 (15761.4 Mb)  TX bytes:771353563 (735.6 Mb)
          Interrupt:16 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:175750 errors:0 dropped:0 overruns:0 frame:0
          TX packets:175750 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:127064217 (121.1 Mb)  TX bytes:127064217 (121.1 Mb)



 # cat /etc/sysconfig/network/ifcfg-eth0 
BOOTPROTO='dhcp'
STARTMODE='auto'
#2

You’ll have to figure out why your system is broadcasting (trying to communicate) using a self-generated address instead of your normal interface address. Could be any kind of misconfiguration.

For a link to the Wikipedia article on martian packets and one guy’s solution to his problem, but the cause of your problem could be anything and unrelated,
https://forums.opensuse.org/showthread.php/510435-Kernel-logging-of-critical-packets-martian-source-KTorrent-seeding?highlight=martian

TSU

#3

Some device on your network broadcasts these packets. Next line after the one you have shown should contain MAC address from this packet so you can find out what device it is.

P.S. You managed to give title that is absolutely unrelated to your actual question.