All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mickael Marchand <marchand@kde.org>
To: netfilter-devel@lists.netfilter.org
Subject: trying to revive rtsp
Date: Sun, 19 Feb 2006 15:13:53 +0100	[thread overview]
Message-ID: <43F87D21.7090305@kde.org> (raw)

Hi,

I am really a newbie to the netfilter coding world, so please forgive
any stupid questions :)

I have mostly ported the old rtsp conntrack+nat code to recent 2.6
kernels, compiles and loads fine into the kernel,
but I have some problems to make it work now :)

the initial TCP connexion to the RTSP server:554 is correctly detected
and the expectation packet seems to be properly setup :
cat /proc/net/ip_conntrack_expect
255 proto=17 src=212.27.38.253 dst=10.0.0.2 sport=0 dport=33302

212.27.38.253 is the RTSP server, 10.0.0.2 is the client, 10.0.0.1 is
the netfilter box.

so once the TCP connexion has been established, we expect a UDP stream
from the server going to the client port 33302.

my problem is that the expected packet does not get through the
netfilter box, I can see the UDP stream coming from the RTSP server and
going to my netfilter box,
the expectation packet seems to get removed of
/proc/net/ip_conntrack_expect as well (so basically it looks all good)
but the netfilter box does not forward packets to 10.0.0.2.
so it looks like a NAT problem to me, maybe the UDP packets are not
getting NAT-ed back to the client.

my first question would be :
is it expected to see 10.0.0.2 in the expected paquet ?
should not it be my external IP instead ?

any tips in what direction I could look ? :)

thanks for any help

Cheers,
Mik
(Please CC-me in answers :)

             reply	other threads:[~2006-02-19 14:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-19 14:13 Mickael Marchand [this message]
2006-02-20 17:36 ` trying to revive rtsp Patrick McHardy
2006-02-21  2:02 ` Punky
  -- strict thread matches above, loose matches on Subject: below --
2006-02-20  7:56 Mickael Marchand

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=43F87D21.7090305@kde.org \
    --to=marchand@kde.org \
    --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.