Re: IPV6 in version 2.4.4

Thanks for the response. 

I can confirm that the recommended settings worked and now IPV6 is working as it should.
If anyone is interested, these are the <listen-socket> settings I am using.


<!-- You may have multiple <listen-socket> elements—> 
<listen-socket> 
<port>8000</port> 
<bind-address>0.0.0.0</bind-address> 
</listen-socket> 

<listen-socket> 
<port>8443</port> 
<bind-address>0.0.0.0</bind-address> 
<ssl>1</ssl> 
</listen-socket> 

<listen-socket> 
<port>8000</port> 
<bind-address>::</bind-address> 
</listen-socket> 

<listen-socket> 
<port>8443</port> 
<bind-address>::</bind-address> 
<ssl>1</ssl> 
</listen-socket>


Thanks
Damian

> On 19 Jan 2023, at 22:54, Philipp Schafft <[email protected]> wrote:
> 
> Good morning,
> 
> On Thu, 2023-01-19 at 13:19 +0100, Marvin Scholz wrote:
>> 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.
> 
> That is true at least for 2.4.x. In 2.5.x I improved that code, plus it
> reports on the dashboard if IPv6 is not available.
> 
> As for 2.4.x and older 2.5.x versions I would suggest to use netstat to
> check the binds and/or configure them more explicitly by binding to ::
> and 0.0.0.0 with two listen sockets. This is also required on systems
> that do not support legacy IP over IPv6 or have it disabled.
> 
> With best regards,
> 
> 
> 
>>>> On 18 Jan 2023, at 08:22, Marvin Scholz <[email protected]>
>>>> 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
> 
> 
> -- 
> Philipp Schafft (CEO/Geschäftsführer) 
> Telephon:  +49.3535 490 17 92
> Website:   https://www.loewenfelsen.net/
> Follow us: https://www.linkedin.com/company/loewenfelsen/
> 
> Löwenfelsen UG (haftungsbeschränkt)     Registration number:
> Bickinger Straße 21                     HRB 12308 CB
> 04916 Herzberg (Elster)                 VATIN/USt-ID:
> Germany                                 DE305133015
> _______________________________________________
> Icecast mailing list
> [email protected]
> http://lists.xiph.org/mailman/listinfo/icecast

_______________________________________________
Icecast mailing list
[email protected]
http://lists.xiph.org/mailman/listinfo/icecast