Odd kernel message error

Seventh · 06-27-2005, 10:35 AM

Hi all,

My RHEL9 install is working great, but my messages file is completley full of this:

Jun 27 11:32:47 kurskx kernel: 129.83.81.157 sent an invalid ICMP type 11, code
0 error to a broadcast: 129.83.81.255 on eth2

Can anyone give me some insight as to what causes this? I've never seen it before, and anything that broadcasts from my server can't be all that good.

Thanks much!

Half_Elf · 06-27-2005, 11:39 AM

well... look like a service on your box broadcast "broken" icmp message. Look which applications are "serving" first (netstat -an might help you ), stop those you don't need and see if you still have these messages. ICMP protocol dont use ports, so it might be harder to find out.
It could also be a "client" application, but it would surprise me, as most "clients" usually dont broadcast for server (but take a look at what you have running anyways?).

No matter what it is, it's nothing a quick iptables script couldn't block

Seventh · 06-28-2005, 09:43 AM

Sorry for the newbie question, I'm not familiar with iptables at all. Is there a quick link somewhere that'd explain how to block the message?

Seventh · 07-05-2005, 02:30 PM

/bump

My logfile:

Quote:

129.83.81.157 sent an invalid ICMP type 11, code 0 error to a broadcast: 129.83
81.255 on eth2
129.83.81.157 sent an invalid ICMP type 11, code 0 error to a broadcast: 129.83
81.255 on eth2
129.83.81.157 sent an invalid ICMP type 11, code 0 error to a broadcast: 129.83
81.255 on eth2
129.83.81.157 sent an invalid ICMP type 11, code 0 error to a broadcast: 129.83
81.255 on eth2
129.83.81.157 sent an invalid ICMP type 11, code 0 error to a broadcast: 129.83
81.255 on eth2
129.83.81.157 sent an invalid ICMP type 11, code 0 error to a broadcast: 129.83
81.255 on eth2
129.83.81.157 sent an invalid ICMP type 11, code 0 error to a broadcast: 129.83
81.255 on eth2
129.83.81.157 sent an invalid ICMP type 11, code 0 error to a broadcast: 129.83
81.255 on eth2
129.83.81.157 sent an invalid ICMP type 11, code 0 error to a broadcast: 129.83
81.255 on eth2
129.83.81.157 sent an invalid ICMP type 11, code 0 error to a broadcast: 129.83
81.255 on eth2
129.83.81.157 sent an invalid ICMP type 11, code 0 error to a broadcast: 129.83
81.255 on eth2
129.83.81.157 sent an invalid ICMP type 11, code 0 error to a broadcast: 129.83
81.255 on eth2
129.83.81.157 sent an invalid ICMP type 11, code 0 error to a broadcast: 129.83
81.255 on eth2
129.83.81.157 sent an invalid ICMP type 11, code 0 error to a broadcast: 129.83
81.255 on eth2
129.83.81.157 sent an invalid ICMP type 11, code 0 error to a broadcast: 129.83
81.255 on eth2
129.83.81.157 sent an invalid ICMP type 11, code 0 error to a broadcast: 129.83
81.255 on eth2
129.83.81.157 sent an invalid ICMP type 11, code 0 error to a broadcast: 129.83
81.255 on eth2
129.83.81.157 sent an invalid ICMP type 11, code 0 error to a broadcast: 129.83
81.255 on eth2
129.83.81.157 sent an invalid ICMP type 11, code 0 error to a broadcast: 129.83
81.255 on eth2
129.83.81.157 sent an invalid ICMP type 11, code 0 error to a broadcast: 129.83
81.255 on eth2
129.83.81.157 sent an invalid ICMP type 11, code 0 error to a broadcast: 129.83
81.255 on eth2
129.83.81.157 sent an invalid ICMP type 11, code 0 error to a broadcast: 129.83
81.255 on eth2
129.83.81.157 sent an invalid ICMP type 11, code 0 error to a broadcast: 129.83
81.255 on eth2
129.83.81.157 sent an invalid ICMP type 11, code 0 error to a broadcast: 129.83
81.255 on eth2
129.83.81.157 sent an invalid ICMP type 11, code 0 error to a broadcast: 129.83
81.255 on eth2
129.83.81.157 sent an invalid ICMP type 11, code 0 error to a broadcast: 129.83
81.255 on eth2

About 50 pages of that.