From: "Stéphane Veyret" <sveyret@gmail.com>
To: Florian Westphal <fw@strlen.de>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: Expectations
Date: Wed, 22 May 2019 08:36:00 +0200 [thread overview]
Message-ID: <CAFs+hh6D5nj7UNBfXt+KPO4vOsWOZHkRY1Lpd1UxwiQJ=5Y-dA@mail.gmail.com> (raw)
In-Reply-To: <20190519201440.sb4ajpd6nuuczrkr@breakpoint.cc>
Le dim. 19 mai 2019 à 22:14, Florian Westphal <fw@strlen.de> a écrit :
> RTSP looks rather complex, wouldn't it be better/simpler to use
> a proxy?
RTSP does not seem that complex to me. It is a bit like FTP: the
client sends a first connection in order to define the ports to use,
then the server initiates the connection on those ports.
I saw some examples of RTSP helper libraries written for old versions
of the kernel (focused on iptables), so I think it would not be very
complicated to port to newest versions.
> We have TPROXY so we can intercept udp and tcp connections; we have
> ctnetlink so the proxy could even inject expectations to keep the real
> data in the kernel forwarding plane.
It would mean we would need to open/expect a very wide range of ports,
if we don't look into the first message to grab the real used port…
By the way, as I had no feedback for the moment regarding expectation
patch I sent (yes, I know it needs time to code review), I just
wondered if I sent them correctly and if they arrived to the mailing
list. They are 4 mails sent on May 17th at about 18:40 CEST. If
someone could just confirm reception, that would be good.
Thank you
Stéphane
next prev parent reply other threads:[~2019-05-22 6:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-18 13:53 Expectations Stéphane Veyret
2019-05-19 20:14 ` Expectations Florian Westphal
2019-05-22 6:36 ` Stéphane Veyret [this message]
2019-05-22 6:42 ` Expectations Florian Westphal
2019-05-22 8:34 ` Expectations Stéphane Veyret
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='CAFs+hh6D5nj7UNBfXt+KPO4vOsWOZHkRY1Lpd1UxwiQJ=5Y-dA@mail.gmail.com' \
--to=sveyret@gmail.com \
--cc=fw@strlen.de \
--cc=netfilter-devel@vger.kernel.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.