All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Gáspár Lajos" <swifty@freemail.hu>
To: Michal Martinek <michal.martinek@siemens.com>
Cc: netfilter@lists.netfilter.org
Subject: Re: netfilter_queue: how to obtain address info from queued packet
Date: Tue, 23 Jan 2007 12:49:11 +0100	[thread overview]
Message-ID: <45B5F637.5030502@freemail.hu> (raw)
In-Reply-To: <45B5E630.6000305@siemens.com>

Michal Martinek írta:
>
> 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.
>
Well... It is not really clear to me what you want... :-) (Blocking some 
"communication" :-) .)
You can drop the whole connection when you detect for example a header 
of a video stream....
This could be dangerous because you would drop some legitimate traffic too.
That is why you have to narrow your matching criterias. (eg.: adding 
some rules like "-i eth0" or "-s 192.168.0.1")
An other good thing to look after is the l7 patch:

http://l7-filter.sourceforge.net/HOWTO

But there may be better solutions if you would clarify more your needs :)

Swifty



  reply	other threads:[~2007-01-23 11:49 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
2007-01-23 11:49         ` Gáspár Lajos [this message]
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=45B5F637.5030502@freemail.hu \
    --to=swifty@freemail.hu \
    --cc=michal.martinek@siemens.com \
    --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.