All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Michael Guntsche <mike@it-loops.com>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: RTSP support for kernels >= 2.6.20
Date: Mon, 16 Apr 2007 16:48:20 +0200	[thread overview]
Message-ID: <46238CB4.3050504@trash.net> (raw)
In-Reply-To: <2AFE2224-4F76-4199-9D41-F9AB48A57E9E@it-loops.com>

Michael Guntsche wrote:
> 
> On Apr 16, 2007, at 15:15, Michael Guntsche wrote:
> 
>>
>> I am sorry, I just wanted to keep the size down.
>> I was able to make some progress today. Both modules compiled and I 
>> see that at least part of it is working.
>> One of the parts of the code I was not able to port is this.
> 
> 
> Answering my own E-Mail. I found my problem with the struct for the  tuple.
> 
> exp->tuple = ((struct nf_conntrack_tuple)
>         {
>           { ct->tuplehash[!dir].tuple.src.u3,
>             { 0 },
>           },
>           {
>             ct->tuplehash[!dir].tuple.dst.u3,
>             { .udp = { htons(expinfo.loport) } },
>             IPPROTO_UDP
>           }
>         });
> 
> This worked. I was not able to get the ->mask correctly though. For 
> testing purposes I used this.
> 
> 
> exp->mask = ((struct nf_conntrack_tuple)
>         {
>           { ct->tuplehash[!dir].tuple.src.u3,
>             { 0 }
>           },
>           {
>             ct->tuplehash[!dir].tuple.src.u3,
>             { .udp = { 0xFFFF } }, 0xFF
>           }
>         });
> 
> and it worked with several test streams. I am pretty sure that this  is
> completely wrong though and I would appreciate an< hints/tips on  how to
> get this right.
> If this is fixed I'll start cleaning everything up and send a patch  to
> the list.


In case you're porting it to nf_conntrack (which is the only thing that
makes sense since ip_conntrack will be gone in 2.6.22), I'd suggest
you use nf_conntrack_expect_init().

  reply	other threads:[~2007-04-16 14:48 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-15 15:31 RTSP support for kernels >= 2.6.20 Michael Guntsche
2007-04-15 19:48 ` Patrick McHardy
2007-04-16 13:15   ` Michael Guntsche
2007-04-16 14:32     ` Michael Guntsche
2007-04-16 14:48       ` Patrick McHardy [this message]
2007-04-16 15:53         ` Michael Guntsche
2007-04-17 22:25           ` Michael Guntsche
2007-04-18  4:33             ` Patrick McHardy
2007-04-18 21:34               ` Michael Guntsche
2007-04-21 12:05                 ` RTSP support for kernels >= 2.6.20 [patchomatic patch] Michael Guntsche
2007-04-21 23:12                   ` Michael Guntsche
2007-04-23 11:42                     ` Patrick McHardy
2007-05-02 20:04                       ` Michael Guntsche
2007-05-03 11:00                         ` Patrick McHardy
2007-05-03 17:18                           ` Michael Guntsche

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=46238CB4.3050504@trash.net \
    --to=kaber@trash.net \
    --cc=mike@it-loops.com \
    --cc=netfilter-devel@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.