From: Stephen Hemminger <stephen@networkplumber.org>
To: Ravish Kumar <ravishk2004@gmail.com>
Cc: Networking <netdev@vger.kernel.org>
Subject: Re: Hooking on L4 Level with process information
Date: Mon, 28 Aug 2017 20:19:00 -0700 [thread overview]
Message-ID: <20170828201900.625a10ed@xeon-e3> (raw)
In-Reply-To: <CAEDnJmJZ1-4DFtjmzDO1US2HCuHYDkcsa+tk8mN3CZ6vcDLbVw@mail.gmail.com>
On Tue, 29 Aug 2017 07:34:51 +0530
Ravish Kumar <ravishk2004@gmail.com> wrote:
> Hi,
>
> I want to hook tcp/udp packets on L4 Layer and based on process
> information , content want to deny or allow packets.
>
> Netfilter provides pre/post Routing hooks but not sure that will be
> right place so thought of asking whether my approach is right.
> Also how i can get process information whether this packet is send by
> this process.
>
> Thoughts /source code reference would be appreciated.
>
> Regards,
> Ravish
There is not a 1:1 relationship between sockets/files and processes.
next prev parent reply other threads:[~2017-08-29 3:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-29 2:04 Hooking on L4 Level with process information Ravish Kumar
2017-08-29 3:19 ` Stephen Hemminger [this message]
2017-08-29 3:36 ` Ravish Kumar
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=20170828201900.625a10ed@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=netdev@vger.kernel.org \
--cc=ravishk2004@gmail.com \
/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.