From: "Egon Phillips" <egon.phillips@sympatico.ca>
To: <netfilter-devel@lists.netfilter.org>
Subject: Owner on Input table
Date: Sat, 12 Feb 2005 19:26:35 -0500 [thread overview]
Message-ID: <000101c51162$aceabfa0$9600a8c0@netcontent> (raw)
I read in the docs that the owner match as described below is not
available on the input chain.
This module attempts to match various
characteristics of the packet creator,
for locally-generated packets. It is
only valid in the OUTPUT chain, and even
this some packets (such as ICMP ping responses)
may have no owner, and hence never match.
Are there any plans to change this policy? If not, is this a limitation
of the software or of the OS? Is it not possible to use the destination
ports process id to determine the owner?
____________________________________________________
The Brockton Initiative (http://brockton.dyndns.org)
Egon Phillips, Chair
next reply other threads:[~2005-02-13 0:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-13 0:26 Egon Phillips [this message]
2005-02-14 7:29 ` Owner on Input table Patrick Schaaf
2005-02-14 7:41 ` Jonas Berlin
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='000101c51162$aceabfa0$9600a8c0@netcontent' \
--to=egon.phillips@sympatico.ca \
--cc=netfilter-devel@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.