All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Shaun T. Erickson" <ste@smxy.org>
To: netfilter@lists.netfilter.org
Subject: Re: incoming interface confusion question
Date: Mon, 21 Jun 2004 15:28:54 -0400	[thread overview]
Message-ID: <40D736F6.50405@smxy.org> (raw)
In-Reply-To: <40D71EC4.7090900@smxy.org>

Shaun T. Erickson wrote:

> Are there any cases where iptables can be confused about what interface 
> a packet came in on? Can a packet arriving on interface A ever be 
> reported as arriving on interface B?
> 
> I had an incident this weekend, and am trying to be certain that the 
> packets came in the interface my system said it did. It's a Red Hat 9 
> system, running their stock 2.4.20-8 kernel.

Please, can anyone answer this for me? I'm trying to prove or disprove a 
theory that would explain an apparent intrusion incident over the 
weekend. It's very important that I know the definitive answer to this. 
Thanks.

	-ste


  reply	other threads:[~2004-06-21 19:28 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-21 17:45 incoming interface confusion question Shaun T. Erickson
2004-06-21 19:28 ` Shaun T. Erickson [this message]
2004-06-21 20:18   ` John A. Sullivan III
2004-06-21 21:13     ` incoming interface confusion question [LONG] Shaun T. Erickson
2004-06-21 22:28       ` incoming interface confusion question Antony Stone
2004-06-21 23:07         ` Shaun T. Erickson
2004-06-22  0:13           ` [SOLVED] " Shaun T. Erickson
2004-06-21 22:33       ` incoming interface confusion question [LONG] John A. Sullivan III
2004-06-22  6:37   ` incoming interface confusion question Jozsef Kadlecsik
2004-06-21 19:36 ` Cedric Blancher
2004-06-21 20:34   ` Ranjeet Shetye
  -- strict thread matches above, loose matches on Subject: below --
2004-06-22 10:56 aksingh
2004-06-22 12:52 ` Shaun T. Erickson

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=40D736F6.50405@smxy.org \
    --to=ste@smxy.org \
    --cc=netfilter@lists.netfilter.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.