From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Ed Street" Subject: RE: Strange log entry ... Date: Mon, 8 Jul 2002 10:39:49 -0400 Sender: netfilter-admin@lists.samba.org Message-ID: <002f01c2268d$5059c5a0$0a01a8c0@ed> References: <1026138591.27153.77.camel@rayw> Reply-To: Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1026138591.27153.77.camel@rayw> Errors-To: netfilter-admin@lists.samba.org List-Help: List-Post: List-Subscribe: , List-Id: List-Unsubscribe: , List-Archive: Content-Type: text/plain; charset="us-ascii" To: 'Raymond Leach' Cc: netfilter@lists.samba.org Hello, Yes it is a reply. See http://www.iana.org/assignments/icmp-parameters Ed -----Original Message----- From: Raymond Leach [mailto:raymondl@knowledgefactory.co.za] Sent: Monday, July 08, 2002 10:30 AM To: blacknet@simplyaquatics.com Cc: netfilter@lists.samba.org Subject: RE: Strange log entry ... On Mon, 2002-07-08 at 16:07, Ed Street wrote: > Hello, > > > Looks like station 10.0.0.19 on eth2 tried to ping 199.181.167.201 and > it was droped. > I've checked the process list on 10.0.0.19 and also restarted it just to make sure, and there is nothing that is trying to ping anywhere. Isn't ICMP CODE 0 TYPE 0 a reply? Doesn't this log entry represent 10.0.0.19's reply to an echo request? Ray > Ed > > -----Original Message----- > From: netfilter-admin@lists.samba.org > [mailto:netfilter-admin@lists.samba.org] On Behalf Of Raymond Leach > Sent: Monday, July 08, 2002 10:07 AM > To: netfilter@lists.samba.org > Subject: Strange log entry ... > > Hi > > Can anyone tell me what this is? > > Jul 8 16:04:23 firefly kernel: DROP FORWARD INTERNAL: IN=eth2 OUT=eth0 > SRC=10.0.0.19 DST=199.181.167.201 LEN=1044 TOS=0x00 PREC=0x00 TTL=254 > ID=18763 DF PROTO=ICMP TYPE=0 CODE=0 ID=6666 SEQ=0 > Jul 8 16:04:26 firefly kernel: DROP FORWARD INTERNAL: IN=eth2 OUT=eth0 > SRC=10.0.0.19 DST=199.181.167.201 LEN=1044 TOS=0x00 PREC=0x00 TTL=254 > ID=18764 DF PROTO=ICMP TYPE=0 CODE=0 ID=6666 SEQ=0 > > I do not allow incoming echo requests to this machine. How the echo > reply is generated beats me ... > > Ray > >