Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Tom Marshall <tommy@home.tig-grr.com>
To: netfilter@lists.netfilter.org
Cc: netfilter-devel@lists.netfilter.org
Subject: Experimental RTSP modules
Date: Sat, 5 Apr 2003 19:35:32 -0800	[thread overview]
Message-ID: <20030406033532.GA23082@home.tig-grr.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1301 bytes --]

Please note this is an experimental module.  It works for me.  It may work
for you, it may panic your kernel, or it may just sit there using ram.

Features:

 * Detects STUN and stays out of the way.
 * Understands proposed client_port=M/N syntax.
 * There is a configurable policy for the destination parameter.

TODO:

 * Handle multiple SETUP messages in a single packet.
 * Un-mangle client_port on return trip.
 * IPv6 modules
 * Much more...

This should work with 2.4.20 and all of 2.4.21-pre# series up to and
including pre7, at least.  It should not work with 2.4.19 or prior.  Please
note that I am making _no_ attempt to support p-o-m or iptables versions not
included in the kernel.  Others may do so if they wish (hey, it's GPL).

The diff was prepared against 2.4.21-pre6.  Please use the "-p1" option to
patch(1) for proper application:
                                
        # cd linux-2.4.21-pre7  
        # cat ../nf-rtsp.diff | patch -p1

Comments (especially bug reports and success reports) welcome.

	http://home.tig-grr.com/nf-rtsp.diff

Hints for implementing IPv6 conntrack and nat modules especially appreciated
(why are there no IRC or FTP modules for IPv6?)

-- 
To use violence is to already be defeated.
        -- Chinese proverb

[-- Attachment #2: Type: application/pgp-signature, Size: 240 bytes --]

             reply	other threads:[~2003-04-06  3:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-06  3:35 Tom Marshall [this message]
2003-05-23 19:58 ` Experimental RTSP modules Harald Welte
2003-05-24 14:30   ` Tom Marshall
2003-05-25 12:12     ` Harald Welte
  -- strict thread matches above, loose matches on Subject: below --
2003-04-06  3:24 Tom Marshall

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=20030406033532.GA23082@home.tig-grr.com \
    --to=tommy@home.tig-grr.com \
    --cc=netfilter-devel@lists.netfilter.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox