November 23, 2024, 05:09:49 AM

News : LinuxSolved.com Linux Help Community Forum..


Author Topic: invalid ICMP error to a broadcast  (Read 6953 times)

Offline muthu

  • Linux Noob !
  • *
  • Posts: 17
invalid ICMP error to a broadcast
« on: April 13, 2005, 05:24:33 AM »
hello sir,


I am using redhat linux 9 .

I am getting one problem.

203.101.45.1 sent an invalid ICMP error to a broadcast



if any solution

please help me.

thanks and regards

s.muthu.

Offline anil_garg5

  • Linux Learner
  • ***
  • Posts: 71
invalid ICMP error to a broadcast
« Reply #1 on: April 13, 2005, 07:15:33 AM »
I am able to ping this address. this IP address is working fine

check if there may be some firewall setting in your LAN or your system.
ping commands usesICMP packets.

#iptables -L (list the iptables rules)
#iptables -F( flushes these rules)
#iptables-save( save these rules)

Offline Ricky

  • LST CareTaker
  • Specially Skilled
  • *****
  • Posts: 2381
invalid ICMP error to a broadcast
« Reply #2 on: April 13, 2005, 12:47:46 PM »
There could be many reasons..
but the error actually saying that.. your machine had sent a packet and in reply that machine (203.101.45.1 ) sent some but they are having some sort of error.
From what I have heard uptill now it is mostly faced by people running nmbd and smbd on their machine..

it is nothing to worry about.. u can ignore them.. to do so ..
Code: [Select]
echo 1 >/proc/sys/net/ipv4/icmp_ignore_bogus_error_responses

It can be also that if that remote machine is having misconfigure tcp ip stack !

Offline bilkay

  • Linux Noob !
  • *
  • Posts: 4
invalid ICMP error to a broadcast
« Reply #3 on: May 01, 2005, 11:36:32 PM »
I've been getting the same message (RH 9 - Shrike) from 10.124.32.1. I looked up the address in http://ws.arin.net/cgi-bin/whois.pl and found it to be:

OrgName:    Internet Assigned Numbers Authority
OrgID:      IANA
Address:    4676 Admiralty Way, Suite 330
City:       Marina del Rey
StateProv:  CA
PostalCode: 90292-6695
Country:    US

Whenever I traceroute anything, 10.124.32.1 is the first address that shows up. I looked up the IP address you're getting messages from and it's:

OrgName:    Asia Pacific Network Information Centre
OrgID:      APNIC
Address:    PO Box 2131
City:       Milton
StateProv:  QLD
PostalCode: 4064
Country:    AU

So  it doesn't look like anything malicious, it just fills the message log, and that can be taken care of as someone else noted:
echo 1 > /proc/sys/net/ipv4/icmp_ignore_bogus_error_responses

One thing I still don't understand is this which appeared in the message log similarly on multiple occasions:

Apr 30 10:36:01 localhost dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Apr 30 10:36:01 localhost dhclient: DHCPACK from 10.124.32.1
Apr 30 10:36:01 localhost dhclient: bound to {myipaddress} -- renewal in 138285 seconds.