From: Michal Martinek <michal.martinek@siemens.com>
To: "Gáspár Lajos" <swifty@freemail.hu>
Cc: netfilter@lists.netfilter.org
Subject: Re: netfilter_queue: how to obtain address info from queued packet
Date: Tue, 23 Jan 2007 11:40:48 +0100 [thread overview]
Message-ID: <45B5E630.6000305@siemens.com> (raw)
In-Reply-To: <45B5E321.90608@freemail.hu>
Gáspár Lajos wrote:
>
> Michal Martinek írta:
>>
>>
>> Gáspár Lajos wrote:
>>>
>>> Michal Martinek írta:
>>>> Hello all,
>>>>
>>>> I am quite a newbie to the netfilter world, so maybe my approach is
>>>> naive. I would like to block communication coming from/to some ports
>>>> according to the content of packets. Unfortunately these ports are
>>>> not static, so port specific netfilter rule cannot be used. So my
>>>> question is:
>>>>
>>> Do you know the STRING module ?
>>
>> I'm afraid not. Can you give me some explanation (or link)?
> Well... :) man iptables...
> iptables -A FORWARD -j DROP -p tcp -m string --string 'Some string'
> --algo kmp
Thanks, I was too fast to answer without looking into man pages:-). But
this module would just save me some work with analyzing packets. The
problem is that I would like to detect video stream in which I can
recognize only some "key packets". The rest is (for me) unrecongnizable
and I only know that they are coming from/to the same port.
>>
>>>> Is it possible to obtain some address info (source/destination
>>>> address and ports) from the packet queued from netfilter?
>>
>>
>
>
next prev parent reply other threads:[~2007-01-23 10:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-23 10:03 netfilter_queue: how to obtain address info from queued packet Michal Martinek
2007-01-23 10:10 ` Gáspár Lajos
2007-01-23 10:18 ` Michal Martinek
2007-01-23 10:27 ` Gáspár Lajos
2007-01-23 10:40 ` Michal Martinek [this message]
2007-01-23 11:49 ` Gáspár Lajos
2007-01-23 10:31 ` Cedric Blancher
2007-01-23 11:53 ` Michal Martinek
2007-01-23 12:33 ` Cedric Blancher
2007-01-23 12:50 ` Michal Martinek
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=45B5E630.6000305@siemens.com \
--to=michal.martinek@siemens.com \
--cc=netfilter@lists.netfilter.org \
--cc=swifty@freemail.hu \
/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.