Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Raymond Leach <raymondl@knowledgefactory.co.za>
To: blacknet@simplyaquatics.com
Cc: netfilter@lists.samba.org
Subject: RE: Strange log entry ...
Date: 08 Jul 2002 16:29:51 +0200	[thread overview]
Message-ID: <1026138591.27153.77.camel@rayw> (raw)
In-Reply-To: <002d01c22688$cfa8a920$0a01a8c0@ed>

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
> 
> 



  reply	other threads:[~2002-07-08 14:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-08 14:07 Strange log entry Raymond Leach
2002-07-08 14:07 ` Ed Street
2002-07-08 14:29   ` Raymond Leach [this message]
2002-07-08 14:36     ` Ramin Alidousti
2002-07-08 17:15       ` Ramin Alidousti
2002-07-08 14:39     ` Ed Street

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1026138591.27153.77.camel@rayw \
    --to=raymondl@knowledgefactory.co.za \
    --cc=blacknet@simplyaquatics.com \
    --cc=netfilter@lists.samba.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox