From: Harald Welte <laforge@netfilter.org>
To: Tom Marshall <tommy@home.tig-grr.com>
Cc: netfilter@lists.netfilter.org, netfilter-devel@lists.netfilter.org
Subject: Re: Experimental RTSP modules
Date: Fri, 23 May 2003 21:58:43 +0200 [thread overview]
Message-ID: <20030523195843.GQ3077@sunbeam.de.gnumonks.org> (raw)
In-Reply-To: <20030406033532.GA23082@home.tig-grr.com>
[-- Attachment #1: Type: text/plain, Size: 1143 bytes --]
On Sat, Apr 05, 2003 at 07:35:32PM -0800, Tom Marshall wrote:
> 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.
great news. If you could convert it to patch-o-matic format, I'm happy
to include it!
> * Handle multiple SETUP messages in a single packet.
> * Un-mangle client_port on return trip.
Any progress so far?
> * IPv6 modules
ipv6 is not supported by conntrack or NAT, so I guess that's going to be
hard to support :) This is has been discussed quite a number of times
on the devel list.
> Hints for implementing IPv6 conntrack and nat modules especially appreciated
> (why are there no IRC or FTP modules for IPv6?)
see above...
--
- Harald Welte <laforge@netfilter.org> http://www.netfilter.org/
============================================================================
"Fragmentation is like classful addressing -- an interesting early
architectural error that shows how much experimentation was going
on while IP was being designed." -- Paul Vixie
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-05-23 19:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-06 3:35 Experimental RTSP modules Tom Marshall
2003-05-23 19:58 ` Harald Welte [this message]
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=20030523195843.GQ3077@sunbeam.de.gnumonks.org \
--to=laforge@netfilter.org \
--cc=netfilter-devel@lists.netfilter.org \
--cc=netfilter@lists.netfilter.org \
--cc=tommy@home.tig-grr.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox