All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vlad <vlad@breyter.com>
To: netfilter@vger.kernel.org
Subject: pid-owner matcher
Date: Tue, 06 Oct 2009 16:17:44 -0400	[thread overview]
Message-ID: <1254860264.15147.4.camel@temp> (raw)

Looking that the Packet Filtering HOWTO it describes an owner extension
that should allow you to match based on uid, gid, pid, and sid. However,
when i try to use the pid matching i get the following error:

bash$ sudo iptables -A OUTPUT -p TCP -m owner --pid-owner 1001 -j MARK
--set-mark 91
>> iptables v1.4.1.1: Unknown arg `--pid-owner'

it appears that pid-owner is no longer a supported option:
bash$ sudo iptables -m owner --help
>>....
>> owner match options:
[!] --uid-owner userid[-userid]      Match local UID
[!] --gid-owner groupid[-groupid]    Match local GID
[!] --socket-exists                  Match if socket exists

Is there any way to get a pid matcher anymore? What I'm trying to do is
to force all traffic generated by a particular process to use a virtual
interface eht0:1. My current approach is to first  --set-mark all such
packets with iptables and then route them using ip rule.


                 reply	other threads:[~2009-10-06 20:17 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1254860264.15147.4.camel@temp \
    --to=vlad@breyter.com \
    --cc=netfilter@vger.kernel.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.