From: Marton Balint via ffmpeg-devel <ffmpeg-devel@ffmpeg.org> To: Peter Enderborg via ffmpeg-devel <ffmpeg-devel@ffmpeg.org> Cc: Marton Balint <cus@passwd.hu> Subject: [FFmpeg-devel] Re: [PATCH v3 5/5] doc/protocols: Add command-line description for ipv6 options Date: Sat, 30 Aug 2025 02:06:52 +0200 (CEST) Message-ID: <4b22a46f-9d49-b729-889f-c6fcef5c71ac@passwd.hu> (raw) In-Reply-To: <20250829140459.3220037-6-peterend@axis.com> On Fri, 29 Aug 2025, Peter Enderborg via ffmpeg-devel wrote: > Two new options added for receive IPv6 multicast streams. > 1 multicast_max_joins > 2 multicast_interface > > Change-Id: Ief0389815cff3edf26f7db5cbff033ce8bb24639 > Signed-off-by: Peter Enderborg <peterend@axis.com> > --- > doc/protocols.texi | 17 ++++++++++++++++- > 1 file changed, 16 insertions(+), 1 deletion(-) > > diff --git a/doc/protocols.texi b/doc/protocols.texi > index 6b582fde30..3def969dbe 100644 > --- a/doc/protocols.texi > +++ b/doc/protocols.texi > @@ -1207,7 +1207,15 @@ This is a deprecated option. Instead, @option{localrtpport} should be > used. > > @item localaddr=@var{addr} > -Local IP address of a network interface used for sending packets or joining > +Local IP address of a network interface used for sending or receiving packets or joining > +multicast groups. > + > +@item multicast_interface=@var{interfacename} > +Local IP address of a network interface used for receiving packets or joining > +multicast groups. Why is this not simply "interface"? I would expect this option to be interchangable with localaddr at least for ipv4, so the user can decide to specify the interface by its ip address or its name. > + > +@item multicast_max_join=@var{n} > +Local IP address of a network interface used for receiving packets or joining > multicast groups. This seems like unintended copy paste. What is the actual use case for this option? How it is decided which additional interfaces are used for multicast? How does this option relates to the localaddr and interface options? > > @item timeout=@var{n} > @@ -1229,6 +1237,13 @@ port will be used for the local RTP and RTCP ports. > @item > If @option{localrtcpport} (the local RTCP port) is not set it will be > set to the local RTP port value plus 1. > + > +@item > +On IPv6 the default receive behavior is using outgoing routing table for selection of > +a interface for multicast streams. With @option{multicast_max_join} receiving > +can be added for multiple interfaces. With @option{multicast_interface} a > +interface is directly selected for receiving. > + I guess this paragraph belongs to the earlier part. > @end enumerate Please merge the documentation patch with corresponding feature patches. Thanks, Marton _______________________________________________ ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org
prev parent reply other threads:[~2025-08-30 0:09 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <0250811223419.GF29660@pb2> 2025-08-29 14:04 ` [FFmpeg-devel] [PATCH v3 0/5] Select output interfaces for ipv6 multicast Peter Enderborg via ffmpeg-devel 2025-08-29 14:04 ` [FFmpeg-devel] [PATCH v3 1/5] configure: Add test_ioctl and test for SIOCGIFINDEX Peter Enderborg via ffmpeg-devel 2025-08-29 17:38 ` [FFmpeg-devel] " Rémi Denis-Courmont via ffmpeg-devel 2025-08-29 14:04 ` [FFmpeg-devel] [PATCH v3 2/5] avformat/udp: Select output interfaces for ipv6 multicast Peter Enderborg via ffmpeg-devel 2025-08-29 14:04 ` [FFmpeg-devel] [PATCH v3 3/5] libavformat: udp.c Add support for multi or single join Peter Enderborg via ffmpeg-devel 2025-08-29 14:04 ` [FFmpeg-devel] [PATCH v3 4/5] libavformat: add multicast interface Peter Enderborg via ffmpeg-devel 2025-08-29 14:04 ` [FFmpeg-devel] [PATCH v3 5/5] doc/protocols: Add command-line description for ipv6 options Peter Enderborg via ffmpeg-devel 2025-08-30 0:06 ` Marton Balint via ffmpeg-devel [this message]
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=4b22a46f-9d49-b729-889f-c6fcef5c71ac@passwd.hu \ --to=ffmpeg-devel@ffmpeg.org \ --cc=cus@passwd.hu \ /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