From: Camille Oudot <camille+ffmpeg-devel@voila.events>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] avformat/rtpproto: add support for RTP/UDP socket reuse
Date: Mon, 26 Dec 2022 00:52:22 +0100
Message-ID: <a7c7b2f8c09e5b895fd2d10853f7e95677c14501.camel@voila.events> (raw)
In-Reply-To: <161CB574-83C0-43B8-A1C7-11D90456DFD2@remlab.net>
On Sun, 2022-12-25 at 11:00 +0100, Rémi Denis-Courmont wrote:
> Again, there is also REUSEPORT, which is what you'd want on Linux in
> this case, but behaves differently on BSD and doesn't exist at all on
> Windows (IIRC).
That option is indeed preferable for security. It works equally good
for the muxing use case, on Linux, with UDP sockets. I don't see why
not using it instead, will do it in a new version of the patch.
> So even for sending, I don't think this patch really works.
REUSEADDR and thus this patch _are_ working well on Linux, with sockets
that only send datagrams. It might behave differently on other systems
though: I've read it is impossible to open two sockets having the same
proto/src IP/src port/dst IP/dst port on BSD systems, but I don't have
one handy. I will try it ASAP.
What is the project's policy on options that are incompatible with some
systems, or that behave differently?
Regards
--
Camille
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next prev parent reply other threads:[~2022-12-25 23:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-22 15:28 Camille Oudot
2022-12-22 15:42 ` Camille Oudot
2022-12-22 19:32 ` Nicolas George
2022-12-24 11:36 ` Rémi Denis-Courmont
2022-12-24 13:07 ` Camille Oudot
2022-12-25 10:00 ` Rémi Denis-Courmont
2022-12-25 23:52 ` Camille Oudot [this message]
2022-12-26 3:20 ` "zhilizhao(赵志立)"
2022-12-26 21:47 ` Nicolas George
2022-12-27 0:46 ` "zhilizhao(赵志立)"
2022-12-31 19:34 ` Rémi Denis-Courmont
2023-01-03 9:03 ` Camille Oudot
2023-01-03 16:03 ` Rémi Denis-Courmont
2023-01-03 19:13 ` Camille Oudot
2023-01-03 19:43 ` Nicolas George
2023-01-04 11:24 ` Camille Oudot
2023-01-05 12:16 ` Nicolas George
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=a7c7b2f8c09e5b895fd2d10853f7e95677c14501.camel@voila.events \
--to=camille+ffmpeg-devel@voila.events \
--cc=ffmpeg-devel@ffmpeg.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
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git