Another question: I see in the icecast config it states that "If a bind-address is not specified for a particular listen-socket, then the socket will be bound to all interfaces (including IPv6 if available). ? Are there any checks / tests that I could do at my end show if it is configured for IPV6 connections? The one below doesn?t seem to confirm that it?s configured that way. ? Damian> On 18 Jan 2023, at 08:22, Marvin Scholz <epirat07 at gmail.com> wrote: > > On 17 Jan 2023, at 23:16, Damian wrote: > >> Thanks for this. I?m on a Debian server so it?s looking good. >> > > Yes, then there should be no issues whatsoever using IPv6 with > Icecast 2.4-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.xiph.org/pipermail/icecast/attachments/20230119/84b45712/attachment.htm> -------------- next part -------------- A non-text attachment was scrubbed... Name: image.jpeg Type: image/jpeg Size: 30618 bytes Desc: not available URL: <http://lists.xiph.org/pipermail/icecast/attachments/20230119/84b45712/attachment.jpeg>
On 18 Jan 2023, at 22:56, Damian wrote:> Another question: I see in the icecast config it states that "If a bind-address is not specified for a particular listen-socket, then the socket will be bound to all interfaces (including IPv6 if available). ? > > Are there any checks / tests that I could do at my end show if it is configured for IPV6 connections? The one below doesn?t seem to confirm that it?s configured that way. >If I remember correctly, on Linux it depends on the system configuration if a socket binds both IPv4 and IPv6 or not.> ? > > > Damian > >> On 18 Jan 2023, at 08:22, Marvin Scholz <epirat07 at gmail.com> wrote: >> >> On 17 Jan 2023, at 23:16, Damian wrote: >> >>> Thanks for this. I?m on a Debian server so it?s looking good. >>> >> >> Yes, then there should be no issues whatsoever using IPv6 with >> Icecast 2.4> _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast