From: Tom Marshall <tommy@home.tig-grr.com>
To: Harald Welte <laforge@netfilter.org>,
netfilter@lists.netfilter.org,
netfilter-devel@lists.netfilter.org
Subject: Re: Experimental RTSP modules
Date: Sat, 24 May 2003 07:30:23 -0700 [thread overview]
Message-ID: <20030524143023.GA31579@home.tig-grr.com> (raw)
In-Reply-To: <20030523195843.GQ3077@sunbeam.de.gnumonks.org>
[-- Attachment #1: Type: text/plain, Size: 1185 bytes --]
On Fri, May 23, 2003 at 09:58:43PM +0200, Harald Welte wrote:
> 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!
Thank you.
I am interested in getting the module into the mainline kernel. I believe
this is where the majority of users are. I have not and will not use p-o-m.
I will convert the patch to use kernel coding standards if someone would
sponsor the change to the 2.4 kernel, but any changes necessary to use p-o-m
will need to be done by someone else because I have zero interest.
> > * Handle multiple SETUP messages in a single packet.
> > * Un-mangle client_port on return trip.
>
> Any progress so far?
Well, no feedback so far at all so I have left the code alone for the
moment. I'm sure you are familiar with the phenomenon. ;-)
--
Football combines the two worst features of American life.
It is violence punctuated by committee meetings.
-- George F. Will
[-- Attachment #2: Type: application/pgp-signature, Size: 240 bytes --]
next prev parent reply other threads:[~2003-05-24 14:30 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
2003-05-24 14:30 ` Tom Marshall [this message]
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=20030524143023.GA31579@home.tig-grr.com \
--to=tommy@home.tig-grr.com \
--cc=laforge@netfilter.org \
--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