From db76 at riseup.net  Tue Jan 17 21:51:07 2023
From: db76 at riseup.net (Damian)
Date: Wed, 18 Jan 2023 07:51:07 +1000
Subject: [Icecast] IPV6 in version 2.4.4
Message-ID: <D665A1FE-4828-4266-9578-89BEB1FC49A0@riseup.net>

Hi,

I would like to know whether Icecast version 2.4.4 supports IPV6 listener connections? I have some mobile phone users that connect to my web server with an IPV6 address but then connect to the Icecast server via IPV4. I assume that IPV6 is supported in version 2.5, but I am not able to upgrade to that version just yet. If it is supported in version 2.4.4, can anyone refer to me to documentation for setting this up in the config? I can?t seem to find anything in the official docs right now.


Damian 

From epirat07 at gmail.com  Tue Jan 17 21:59:18 2023
From: epirat07 at gmail.com (Marvin Scholz)
Date: Tue, 17 Jan 2023 22:59:18 +0100
Subject: [Icecast] IPV6 in version 2.4.4
In-Reply-To: <D665A1FE-4828-4266-9578-89BEB1FC49A0@riseup.net>
References: <D665A1FE-4828-4266-9578-89BEB1FC49A0@riseup.net>
Message-ID: <D6CA3DB0-72DB-458B-A896-A2635D7C7653@gmail.com>

Hi,

On 17 Jan 2023, at 22:51, Damian wrote:

> Hi,
>
> I would like to know whether Icecast version 2.4.4 supports IPV6 listener connections? I have some mobile phone users that connect to my web server with an IPV6 address but then connect to the Icecast server via IPV4. I assume that IPV6 is supported in version 2.5, but I am not able to upgrade to that version just yet. If it is supported in version 2.4.4, can anyone refer to me to documentation for setting this up in the config? I can?t seem to find anything in the official docs right now.

If your server is a Windows server, see https://gitlab.xiph.org/xiph/icecast-server/-/issues/2458

>
>
> Damian
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast


From db76 at riseup.net  Tue Jan 17 22:16:39 2023
From: db76 at riseup.net (Damian)
Date: Wed, 18 Jan 2023 08:16:39 +1000
Subject: [Icecast] IPV6 in version 2.4.4
In-Reply-To: <D6CA3DB0-72DB-458B-A896-A2635D7C7653@gmail.com>
References: <D665A1FE-4828-4266-9578-89BEB1FC49A0@riseup.net>
 <D6CA3DB0-72DB-458B-A896-A2635D7C7653@gmail.com>
Message-ID: <1B079B59-B455-48FF-9F85-9DE8EAADB5F3@riseup.net>

Thanks for this. I?m on a Debian server so it?s looking good.  

> On 18 Jan 2023, at 07:59, Marvin Scholz <epirat07 at gmail.com> wrote:
> 
> Hi,
> 
> On 17 Jan 2023, at 22:51, Damian wrote:
> 
>> Hi,
>> 
>> I would like to know whether Icecast version 2.4.4 supports IPV6 listener connections? I have some mobile phone users that connect to my web server with an IPV6 address but then connect to the Icecast server via IPV4. I assume that IPV6 is supported in version 2.5, but I am not able to upgrade to that version just yet. If it is supported in version 2.4.4, can anyone refer to me to documentation for setting this up in the config? I can?t seem to find anything in the official docs right now.
> 
> If your server is a Windows server, see https://gitlab.xiph.org/xiph/icecast-server/-/issues/2458
> 
>> 
>> 
>> Damian
>> _______________________________________________
>> Icecast mailing list
>> Icecast at xiph.org
>> http://lists.xiph.org/mailman/listinfo/icecast
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast



From epirat07 at gmail.com  Tue Jan 17 22:22:46 2023
From: epirat07 at gmail.com (Marvin Scholz)
Date: Tue, 17 Jan 2023 23:22:46 +0100
Subject: [Icecast] IPV6 in version 2.4.4
In-Reply-To: <1B079B59-B455-48FF-9F85-9DE8EAADB5F3@riseup.net>
References: <D665A1FE-4828-4266-9578-89BEB1FC49A0@riseup.net>
 <D6CA3DB0-72DB-458B-A896-A2635D7C7653@gmail.com>
 <1B079B59-B455-48FF-9F85-9DE8EAADB5F3@riseup.net>
Message-ID: <ECA4D9E1-E65C-4CC0-AB06-B3D0DB05CC34@gmail.com>

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

>> On 18 Jan 2023, at 07:59, Marvin Scholz <epirat07 at gmail.com> wrote:
>>
>> Hi,
>>
>> On 17 Jan 2023, at 22:51, Damian wrote:
>>
>>> Hi,
>>>
>>> I would like to know whether Icecast version 2.4.4 supports IPV6 listener connections? I have some mobile phone users that connect to my web server with an IPV6 address but then connect to the Icecast server via IPV4. I assume that IPV6 is supported in version 2.5, but I am not able to upgrade to that version just yet. If it is supported in version 2.4.4, can anyone refer to me to documentation for setting this up in the config? I can?t seem to find anything in the official docs right now.
>>
>> If your server is a Windows server, see https://gitlab.xiph.org/xiph/icecast-server/-/issues/2458
>>
>>>
>>>
>>> Damian
>>> _______________________________________________
>>> Icecast mailing list
>>> Icecast at xiph.org
>>> http://lists.xiph.org/mailman/listinfo/icecast
>> _______________________________________________
>> Icecast mailing list
>> Icecast at xiph.org
>> http://lists.xiph.org/mailman/listinfo/icecast
>
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast


From db76 at riseup.net  Wed Jan 18 21:56:02 2023
From: db76 at riseup.net (Damian)
Date: Thu, 19 Jan 2023 07:56:02 +1000
Subject: [Icecast] IPV6 in version 2.4.4
In-Reply-To: <ECA4D9E1-E65C-4CC0-AB06-B3D0DB05CC34@gmail.com>
References: <D665A1FE-4828-4266-9578-89BEB1FC49A0@riseup.net>
 <D6CA3DB0-72DB-458B-A896-A2635D7C7653@gmail.com>
 <1B079B59-B455-48FF-9F85-9DE8EAADB5F3@riseup.net>
 <ECA4D9E1-E65C-4CC0-AB06-B3D0DB05CC34@gmail.com>
Message-ID: <7B43107C-D9F7-4D95-9B38-AD06B1590E79@riseup.net>

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>

From epirat07 at gmail.com  Thu Jan 19 12:19:26 2023
From: epirat07 at gmail.com (Marvin Scholz)
Date: Thu, 19 Jan 2023 13:19:26 +0100
Subject: [Icecast] IPV6 in version 2.4.4
In-Reply-To: <7B43107C-D9F7-4D95-9B38-AD06B1590E79@riseup.net>
References: <D665A1FE-4828-4266-9578-89BEB1FC49A0@riseup.net>
 <D6CA3DB0-72DB-458B-A896-A2635D7C7653@gmail.com>
 <1B079B59-B455-48FF-9F85-9DE8EAADB5F3@riseup.net>
 <ECA4D9E1-E65C-4CC0-AB06-B3D0DB05CC34@gmail.com>
 <7B43107C-D9F7-4D95-9B38-AD06B1590E79@riseup.net>
Message-ID: <E4DBA14F-4DE9-49BE-9860-B6165D2FDB34@gmail.com>


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


From phschafft at de.loewenfelsen.net  Thu Jan 19 12:54:54 2023
From: phschafft at de.loewenfelsen.net (Philipp Schafft)
Date: Thu, 19 Jan 2023 12:54:54 +0000
Subject: [Icecast] IPV6 in version 2.4.4
In-Reply-To: <E4DBA14F-4DE9-49BE-9860-B6165D2FDB34@gmail.com>
References: <D665A1FE-4828-4266-9578-89BEB1FC49A0@riseup.net>
 <D6CA3DB0-72DB-458B-A896-A2635D7C7653@gmail.com>
 <1B079B59-B455-48FF-9F85-9DE8EAADB5F3@riseup.net>
 <ECA4D9E1-E65C-4CC0-AB06-B3D0DB05CC34@gmail.com>
 <7B43107C-D9F7-4D95-9B38-AD06B1590E79@riseup.net>
 <E4DBA14F-4DE9-49BE-9860-B6165D2FDB34@gmail.com>
Message-ID: <1164481ab3b3fbc01d6a46e12b9ae8c752f227c7.camel@de.loewenfelsen.net>

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 <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


-- 
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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: This is a digitally signed message part
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20230119/a701e255/attachment.sig>

From verten at xs4all.nl  Thu Jan 19 12:54:23 2023
From: verten at xs4all.nl (Verten Radio)
Date: Thu, 19 Jan 2023 13:54:23 +0100
Subject: [Icecast] How to get https stream in icecast under windows server
Message-ID: <654a3f9e-97f8-11ed-87f0-00505699772e@smtp.kpnmail.nl>

Looking for  instructions to set up https access for icecast server under windows server.

The main problem is that openssl problably isn?t installed.

What is the best way to install openssl and where can i download this program for windows.

Regards,

Johan



Verzonden vanuit Mail voor Windows

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20230119/998d0190/attachment.htm>

From db76 at riseup.net  Fri Jan 20 08:01:00 2023
From: db76 at riseup.net (Damian)
Date: Fri, 20 Jan 2023 18:01:00 +1000
Subject: [Icecast] IPV6 in version 2.4.4
In-Reply-To: <1164481ab3b3fbc01d6a46e12b9ae8c752f227c7.camel@de.loewenfelsen.net>
References: <D665A1FE-4828-4266-9578-89BEB1FC49A0@riseup.net>
 <D6CA3DB0-72DB-458B-A896-A2635D7C7653@gmail.com>
 <1B079B59-B455-48FF-9F85-9DE8EAADB5F3@riseup.net>
 <ECA4D9E1-E65C-4CC0-AB06-B3D0DB05CC34@gmail.com>
 <7B43107C-D9F7-4D95-9B38-AD06B1590E79@riseup.net>
 <E4DBA14F-4DE9-49BE-9860-B6165D2FDB34@gmail.com>
 <1164481ab3b3fbc01d6a46e12b9ae8c752f227c7.camel@de.loewenfelsen.net>
Message-ID: <DCB1CD6C-486B-4FC9-9E70-BEE50D7BDCAB@riseup.net>

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 <phschafft at de.loewenfelsen.net> 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 <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
> 
> 
> -- 
> 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
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast



From db76 at riseup.net  Fri Jan 20 11:47:06 2023
From: db76 at riseup.net (Damian)
Date: Fri, 20 Jan 2023 21:47:06 +1000
Subject: [Icecast] IPV6 in version 2.4.4
In-Reply-To: <DCB1CD6C-486B-4FC9-9E70-BEE50D7BDCAB@riseup.net>
References: <D665A1FE-4828-4266-9578-89BEB1FC49A0@riseup.net>
 <D6CA3DB0-72DB-458B-A896-A2635D7C7653@gmail.com>
 <1B079B59-B455-48FF-9F85-9DE8EAADB5F3@riseup.net>
 <ECA4D9E1-E65C-4CC0-AB06-B3D0DB05CC34@gmail.com>
 <7B43107C-D9F7-4D95-9B38-AD06B1590E79@riseup.net>
 <E4DBA14F-4DE9-49BE-9860-B6165D2FDB34@gmail.com>
 <1164481ab3b3fbc01d6a46e12b9ae8c752f227c7.camel@de.loewenfelsen.net>
 <DCB1CD6C-486B-4FC9-9E70-BEE50D7BDCAB@riseup.net>
Message-ID: <089BD697-69CD-49A5-9FB9-AAE0E4115753@riseup.net>

Apologies, one more question. With the edited icecast configuration I provided in my previous reply, netstat now shows the IPV6 binds but not the IPV4 binds. To your knowledge, does this seem correct? The Icecast server seems to be working properly and is accepting listener connections with IPV4 addresses. Just trying to understand why I don?t see 0.0.0.0:8000 for instance.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screenshot 2023-01-20 at 21.40.02.png
Type: image/png
Size: 101817 bytes
Desc: not available
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20230120/3d3b8394/attachment.png>
-------------- next part --------------


> On 20 Jan 2023, at 18:01, Damian <db76 at riseup.net> wrote:
> 
> 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 <phschafft at de.loewenfelsen.net> 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 <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
>> 
>> 
>> -- 
>> 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
>> Icecast at xiph.org
>> http://lists.xiph.org/mailman/listinfo/icecast
> 


From db76 at riseup.net  Fri Jan 20 12:14:32 2023
From: db76 at riseup.net (Damian)
Date: Fri, 20 Jan 2023 22:14:32 +1000
Subject: [Icecast] IPV6 in version 2.4.4
In-Reply-To: <089BD697-69CD-49A5-9FB9-AAE0E4115753@riseup.net>
References: <D665A1FE-4828-4266-9578-89BEB1FC49A0@riseup.net>
 <D6CA3DB0-72DB-458B-A896-A2635D7C7653@gmail.com>
 <1B079B59-B455-48FF-9F85-9DE8EAADB5F3@riseup.net>
 <ECA4D9E1-E65C-4CC0-AB06-B3D0DB05CC34@gmail.com>
 <7B43107C-D9F7-4D95-9B38-AD06B1590E79@riseup.net>
 <E4DBA14F-4DE9-49BE-9860-B6165D2FDB34@gmail.com>
 <1164481ab3b3fbc01d6a46e12b9ae8c752f227c7.camel@de.loewenfelsen.net>
 <DCB1CD6C-486B-4FC9-9E70-BEE50D7BDCAB@riseup.net>
 <089BD697-69CD-49A5-9FB9-AAE0E4115753@riseup.net>
Message-ID: <54820AB5-7D26-434D-B597-54E6B343CFAE@riseup.net>

Actually, I think I found the answer. 

On Linux, binding to [::] (IPv6) results in receiving both IPv6 and IPv4 traffic (by default). These are referred to as IPv4-mapped IPv6 addresses. Netstat simply shows the IPv6 entry only, because there's technically only a single bind, that happens to support both IPv4 and IPv6.

> On 20 Jan 2023, at 21:47, Damian <db76 at riseup.net> wrote:
> 
> <Screenshot 2023-01-20 at 21.40.02.png>



From jayaubs89 at gmail.com  Fri Jan 20 12:28:36 2023
From: jayaubs89 at gmail.com (Coolvibes Reloaded)
Date: Fri, 20 Jan 2023 12:28:36 +0000
Subject: [Icecast] IPV6 in version 2.4.4
In-Reply-To: <D665A1FE-4828-4266-9578-89BEB1FC49A0@riseup.net>
References: <D665A1FE-4828-4266-9578-89BEB1FC49A0@riseup.net>
Message-ID: <CAJQJMxq=_n8Lug8XoG1Xdrc+gSx=iGLbmVZEqmH-6Dzjc3p2=w@mail.gmail.com>

I would like to know how I can setup icecast with autodj?

On Tue, 17 Jan 2023, 21:51 Damian, <db76 at riseup.net> wrote:

> Hi,
>
> I would like to know whether Icecast version 2.4.4 supports IPV6 listener
> connections? I have some mobile phone users that connect to my web server
> with an IPV6 address but then connect to the Icecast server via IPV4. I
> assume that IPV6 is supported in version 2.5, but I am not able to upgrade
> to that version just yet. If it is supported in version 2.4.4, can anyone
> refer to me to documentation for setting this up in the config? I can?t
> seem to find anything in the official docs right now.
>
>
> Damian
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20230120/f8a61b0a/attachment.htm>

From phschafft at de.loewenfelsen.net  Fri Jan 20 12:32:59 2023
From: phschafft at de.loewenfelsen.net (Philipp Schafft)
Date: Fri, 20 Jan 2023 12:32:59 +0000
Subject: [Icecast] IPV6 in version 2.4.4
In-Reply-To: <CAJQJMxq=_n8Lug8XoG1Xdrc+gSx=iGLbmVZEqmH-6Dzjc3p2=w@mail.gmail.com>
References: <D665A1FE-4828-4266-9578-89BEB1FC49A0@riseup.net>
 <CAJQJMxq=_n8Lug8XoG1Xdrc+gSx=iGLbmVZEqmH-6Dzjc3p2=w@mail.gmail.com>
Message-ID: <a760efbd419565c1536f7611902d2f8a684c2c5a.camel@de.loewenfelsen.net>

Good morning,

On Fri, 2023-01-20 at 12:28 +0000, Coolvibes Reloaded wrote:
> I would like to know how I can setup icecast with autodj?

How is that related to this thread?


> On Tue, 17 Jan 2023, 21:51 Damian, <db76 at riseup.net> wrote:
> > Hi,
> > 
> > I would like to know whether Icecast version 2.4.4 supports IPV6
> > listener connections? I have some mobile phone users that connect
> > to my web server with an IPV6 address but then connect to the
> > Icecast server via IPV4. I assume that IPV6 is supported in version
> > 2.5, but I am not able to upgrade to that version just yet. If it
> > is supported in version 2.4.4, can anyone refer to me to
> > documentation for setting this up in the config? I can?t seem to
> > find anything in the official docs right now.


-- 
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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: This is a digitally signed message part
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20230120/05993588/attachment.sig>

From phschafft at de.loewenfelsen.net  Fri Jan 20 12:33:29 2023
From: phschafft at de.loewenfelsen.net (Philipp Schafft)
Date: Fri, 20 Jan 2023 12:33:29 +0000
Subject: [Icecast] IPV6 in version 2.4.4
In-Reply-To: <54820AB5-7D26-434D-B597-54E6B343CFAE@riseup.net>
References: <D665A1FE-4828-4266-9578-89BEB1FC49A0@riseup.net>
 <D6CA3DB0-72DB-458B-A896-A2635D7C7653@gmail.com>
 <1B079B59-B455-48FF-9F85-9DE8EAADB5F3@riseup.net>
 <ECA4D9E1-E65C-4CC0-AB06-B3D0DB05CC34@gmail.com>
 <7B43107C-D9F7-4D95-9B38-AD06B1590E79@riseup.net>
 <E4DBA14F-4DE9-49BE-9860-B6165D2FDB34@gmail.com>
 <1164481ab3b3fbc01d6a46e12b9ae8c752f227c7.camel@de.loewenfelsen.net>
 <DCB1CD6C-486B-4FC9-9E70-BEE50D7BDCAB@riseup.net>
 <089BD697-69CD-49A5-9FB9-AAE0E4115753@riseup.net>
 <54820AB5-7D26-434D-B597-54E6B343CFAE@riseup.net>
Message-ID: <69c2dba6428139854d74034654ae2573e0e76852.camel@de.loewenfelsen.net>

Good morning,

On Fri, 2023-01-20 at 22:14 +1000, Damian wrote:
> Actually, I think I found the answer. 
> 
> On Linux, binding to [::] (IPv6) results in receiving both IPv6 and
> IPv4 traffic (by default). These are referred to as IPv4-mapped IPv6
> addresses. Netstat simply shows the IPv6 entry only, because there's
> technically only a single bind, that happens to support both IPv4 and
> IPv6.

yes, you found the correct answer. :)

With best regards,

-- 
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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: This is a digitally signed message part
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20230120/678bf9dc/attachment.sig>

From jayaubs89 at gmail.com  Fri Jan 20 12:38:16 2023
From: jayaubs89 at gmail.com (Coolvibes Reloaded)
Date: Fri, 20 Jan 2023 12:38:16 +0000
Subject: [Icecast] IPV6 in version 2.4.4
In-Reply-To: <a760efbd419565c1536f7611902d2f8a684c2c5a.camel@de.loewenfelsen.net>
References: <D665A1FE-4828-4266-9578-89BEB1FC49A0@riseup.net>
 <CAJQJMxq=_n8Lug8XoG1Xdrc+gSx=iGLbmVZEqmH-6Dzjc3p2=w@mail.gmail.com>
 <a760efbd419565c1536f7611902d2f8a684c2c5a.camel@de.loewenfelsen.net>
Message-ID: <CAJQJMxphE0K2tvPjCne+TdDxmpe084_Jfi8ED+Kx7ywBHBk97w@mail.gmail.com>

Because it's icecast

I would like to know how to use icecast with autodj please

On Fri, 20 Jan 2023, 12:33 Philipp Schafft, <phschafft at de.loewenfelsen.net>
wrote:

> Good morning,
>
> On Fri, 2023-01-20 at 12:28 +0000, Coolvibes Reloaded wrote:
> > I would like to know how I can setup icecast with autodj?
>
> How is that related to this thread?
>
>
> > On Tue, 17 Jan 2023, 21:51 Damian, <db76 at riseup.net> wrote:
> > > Hi,
> > >
> > > I would like to know whether Icecast version 2.4.4 supports IPV6
> > > listener connections? I have some mobile phone users that connect
> > > to my web server with an IPV6 address but then connect to the
> > > Icecast server via IPV4. I assume that IPV6 is supported in version
> > > 2.5, but I am not able to upgrade to that version just yet. If it
> > > is supported in version 2.4.4, can anyone refer to me to
> > > documentation for setting this up in the config? I can?t seem to
> > > find anything in the official docs right now.
>
>
> --
> 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
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20230120/726631c0/attachment.htm>

From jordan at coolmic.net  Fri Jan 20 17:35:20 2023
From: jordan at coolmic.net (Jordan Erickson)
Date: Fri, 20 Jan 2023 09:35:20 -0800
Subject: [Icecast] IPV6 in version 2.4.4
In-Reply-To: <CAJQJMxphE0K2tvPjCne+TdDxmpe084_Jfi8ED+Kx7ywBHBk97w@mail.gmail.com>
References: <D665A1FE-4828-4266-9578-89BEB1FC49A0@riseup.net>
 <CAJQJMxq=_n8Lug8XoG1Xdrc+gSx=iGLbmVZEqmH-6Dzjc3p2=w@mail.gmail.com>
 <a760efbd419565c1536f7611902d2f8a684c2c5a.camel@de.loewenfelsen.net>
 <CAJQJMxphE0K2tvPjCne+TdDxmpe084_Jfi8ED+Kx7ywBHBk97w@mail.gmail.com>
Message-ID: <58b9e332-bc33-e9a0-8852-6f2ae4a9520c@coolmic.net>

Please start a new thread instead of hijacking an existing thread. This 
way everyone on list will be able to separate the discussions correctly. 
Thank you :)


On 1/20/23 04:38, Coolvibes Reloaded wrote:
> Because it's icecast
>
> I would like to know how to use icecast with autodj please
>
> On Fri, 20 Jan 2023, 12:33 Philipp Schafft, 
> <phschafft at de.loewenfelsen.net> wrote:
>
>     Good morning,
>
>     On Fri, 2023-01-20 at 12:28 +0000, Coolvibes Reloaded wrote:
>     > I would like to know how I can setup icecast with autodj?
>
>     How is that related to this thread?
>
>
>     > On Tue, 17 Jan 2023, 21:51 Damian, <db76 at riseup.net> wrote:
>     > > Hi,
>     > >
>     > > I would like to know whether Icecast version 2.4.4 supports IPV6
>     > > listener connections? I have some mobile phone users that connect
>     > > to my web server with an IPV6 address but then connect to the
>     > > Icecast server via IPV4. I assume that IPV6 is supported in
>     version
>     > > 2.5, but I am not able to upgrade to that version just yet. If it
>     > > is supported in version 2.4.4, can anyone refer to me to
>     > > documentation for setting this up in the config? I can?t seem to
>     > > find anything in the official docs right now.
>
>
>     -- 
>     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
>     Icecast at xiph.org
>     http://lists.xiph.org/mailman/listinfo/icecast
>
>
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast

-- 
Jordan Erickson
Project Manager, Cool Mic
https://coolmic.net/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20230120/5a3375ca/attachment.htm>

From hgalt at gmx.net  Sat Jan 28 19:29:13 2023
From: hgalt at gmx.net (HGAlt)
Date: Sat, 28 Jan 2023 20:29:13 +0100
Subject: [Icecast] XSPF file
Message-ID: <000901d9334e$ce275490$6a75fdb0$@gmx.net>

I have figured out, that it is possible to get a xml file, if you add .xspf
to the end of the stream url.

This file includes the number of current listeners and max connections, what
I don't want that this information goes public!



How can I edit the information, which is displayed  in the xsl file?



Thanks for your support,

Hans-Georg







--
Diese E-Mail wurde von Avast-Antivirussoftware auf Viren gepr?ft.
www.avast.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20230128/f56a324c/attachment.htm>

From phschafft at de.loewenfelsen.net  Sat Jan 28 19:32:52 2023
From: phschafft at de.loewenfelsen.net (Philipp Schafft)
Date: Sat, 28 Jan 2023 19:32:52 +0000
Subject: [Icecast] XSPF file
In-Reply-To: <000901d9334e$ce275490$6a75fdb0$@gmx.net>
References: <000901d9334e$ce275490$6a75fdb0$@gmx.net>
Message-ID: <2be6b03e07c6794de5f92a8ed284322e7d6fa9a4.camel@de.loewenfelsen.net>

Good afternoon,

On Sat, 2023-01-28 at 20:29 +0100, HGAlt wrote:
> I have figured out, that it is possible to get a xml file, if you add
> .xspf to the end of the stream url.
> This file includes the number of current listeners and max
> connections, what I don?t want that this information goes public!
>  
> How can I edit the information, which is displayed  in the xsl file?

You can just edit admin/xspf.xsl. It is the template used to generate
that XSPF playlist.


With best regards,

-- 
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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: This is a digitally signed message part
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20230128/f7469394/attachment.sig>

From hgalt at gmx.net  Sat Jan 28 21:26:43 2023
From: hgalt at gmx.net (HGAlt)
Date: Sat, 28 Jan 2023 22:26:43 +0100
Subject: [Icecast] XSPF file
In-Reply-To: <2be6b03e07c6794de5f92a8ed284322e7d6fa9a4.camel@de.loewenfelsen.net>
References: <000901d9334e$ce275490$6a75fdb0$@gmx.net>
 <2be6b03e07c6794de5f92a8ed284322e7d6fa9a4.camel@de.loewenfelsen.net>
Message-ID: <002201d9335f$38313940$a893abc0$@gmx.net>

Thanks Philipp,

I was blind and could not find the file under /admin.

Best regards,
Hans-Georg

-----Urspr?ngliche Nachricht-----
Von: Icecast [mailto:icecast-bounces at xiph.org] Im Auftrag von Philipp Schafft
Gesendet: Samstag, 28. Januar 2023 20:33
An: Icecast streaming server user discussions
Betreff: Re: [Icecast] XSPF file

Good afternoon,

On Sat, 2023-01-28 at 20:29 +0100, HGAlt wrote:
> I have figured out, that it is possible to get a xml file, if you add
> .xspf to the end of the stream url.
> This file includes the number of current listeners and max
> connections, what I don?t want that this information goes public!
>
> How can I edit the information, which is displayed  in the xsl file?

You can just edit admin/xspf.xsl. It is the template used to generate that XSPF playlist.


With best regards,

--
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


--
Diese E-Mail wurde von Avast-Antivirussoftware auf Viren gepr?ft.
www.avast.com


From jayaubs89 at gmail.com  Sun Jan 29 16:35:20 2023
From: jayaubs89 at gmail.com (Coolvibes Reloaded)
Date: Sun, 29 Jan 2023 16:35:20 +0000
Subject: [Icecast] Streaming server
Message-ID: <CAJQJMxr9Hv9hQhtNR5AiTv0ToKx6kffYzQa-qUPvn22=1cif3g@mail.gmail.com>

I would like to know how
I can setup my own streaming server
Port forward I know I have to do

But I would like my presenters to be able to use the stream and for the
stream to be able to work in players as well?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20230129/5fb3c4a2/attachment.htm>

From phschafft at de.loewenfelsen.net  Mon Jan 30 14:24:10 2023
From: phschafft at de.loewenfelsen.net (Philipp Schafft)
Date: Mon, 30 Jan 2023 14:24:10 +0000
Subject: [Icecast] Release of libigloo, version 0.9.2
Message-ID: <af53a34ac0e7c628846fd7155ba18e9a18343809.camel@de.loewenfelsen.net>

Good morning,

the Icecast Project is very pleased to have released the next version
of libigloo, version 0.9.2.

libigloo is a generic C framework which provides us with a common space
for helpers and support routines for other Icecast Project's software.
However it can also be used outside of Icecast context.

The new version:
 * improved the general performance of the string pool,
 * migrated to the librhash as cryptographic hash backend,
 * and fixed a serious bug in the reference counting logic of the ro
   subsystem.

The fixed bug in the reference counting might have effects on security
and stability. We therefore strongly suggest to upgrade.


If you are a downstream maintainer we would like to kindly ask
considering updating packages.

You can find our news entry at:
   https://icecast.org/news/libigloo-release-0_9_2/

Downloads can be found at:
   https://icecast.org/download/#bindings


With best regards,

-- 
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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: This is a digitally signed message part
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20230130/e2ba7b52/attachment.sig>