similar to: Reloading the config to pick up new ssl cert

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

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

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

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 20 Jul 2020, at 1:12, Damian wrote: > I solved the issue by adding my own m3u files to > /usr/share/icecast/web but I am not sure if this is icecast > best-practice. This also raises a few other issues as well… http > stream links don’t appear on the icecast stream directory and stream > titles and track metadata does not display when opening m3u files > created in this

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

I solved the issue by adding my own m3u files to /usr/share/icecast/web but I am not sure if this is icecast best-practice. This also raises a few other issues as well… http stream links don’t appear on the icecast stream directory and stream titles and track metadata does not display when opening m3u files created in this way. I assume that there are various reasons for this…mainly that https

Hi, I installed icecast2 on Debian 10 via backports for buster so that I could get ssl support. I’ve successfully configured iceacst to stream via ssl within the browser. No problems there. For instance I can successfully open a https link to the stream with a URL like https://domain-name.net:8433/mountname <https://domain-name.net:8433/mountname> However, the same URL with .m3u at the

So, I’ll try to explain what I mean a little more by referring to some images. In the first image here, http://systrum.net/mount.png <http://systrum.net/mount.png> iTunes shows the mount-name of my stream. This is not the option that I want, but it is what seems to be the default that I am stuck with. In this second image, http://systrum.net/stream.png <http://systrum.net/stream.png>

Great. Thanks for clarifying all that. > On 15 Jul 2020, at 01:49, Paul Martin <pm at nowster.me.uk> wrote: > > On Tue, Jul 14, 2020 at 06:25:45AM +1000, Damian wrote: >> Thanks for confirming that. So then is the information in the >> article below about SSL support being available in the stable >> versions offered by Xiph incorrect? >> >>

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>

I see. However, it is often pretty easy to see that a duplicate connection is the same listener because the time connected to the server of the two connections is the same. In that case, I am wondering which would be the one to kick. > On 22 Dec 2019, at 23:39, Gavin Stephens <gavin at stephens.net.nz> wrote: > > With NAT, also with carrier grade NAT becoming more poplular with

Hi, When installing Icecast2 (stable) on Debian9 using ATP packet manager, we need to go into /etc/default/icecast and enable the init.d script with ENABLE=true if we want to run Icecast as a service. I?ve been playing with icecast 2.5 beta installed from source and obviously this means things are located in different places. I would like to know if it is also possible to run this version as a

Thanks for your offer to help. Do you mind if I email you at 0turn1 at gmail.com instead?... as I am no longer on facebook. > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: <http://lists.xiph.org/pipermail/icecast/attachments/20190112/cadadb48/attachment-0001.html> > > ------------------------------ > > Message: 2 > Date:

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:

Hi, thanks for your reply. So does that then mean that there is no inbuilt mechanism for forcing stream-name to display over mount-name? I run Liquidsoap with iceacst, and I know Liquidsoap is responsible for the artist and title metadata, but I thought that icecast handled the stream name side of things. Any clarification on this would be helpful. D On Tue Jan 8 14:29:21 UTC 2019 0turn1 at

Hi, My question is specific to installing a version of Icecast2 with support for SSL. Of course I still need to configure the config file with the certificate later, but I’ve read that installing icecast from the xiph repositories at download.opensouse would get me a version with SSL support…doing ... sudo sh -c "echo deb http://download.opensuse.org/repositories/multimedia:/xiph/Debian_10/

Good morning, On Sun, 2020-10-11 at 10:24 +1000, Damian wrote: > Can I also ask, which is the recommended course of action? Sure, just keep in mind that we had weekend, so people were off. ;) > Should I rebuild icecast with OpenSSL or is there now a fixed version > via backports that I can use? Based on... On Sat, 2020-10-10 at 23:06 +1000, Damian wrote: > Edit (apologies for the

Hi again, I apologise for my persistence with this. Perhaps my last question has already been answered in another thread. If so, could anyone please point me to it. Just needing to know how to enable Icecast as a service on Debian when installed from source. The option to enable it isn?t in the same directory (/etc/default/icecast) as when using apt-get install D > On 7 Feb 2019, at 10:28

With NAT, also with carrier grade NAT becoming more poplular with ISP's yet to move to IPv6, if you have a very popular stream you could end up kicking valid listners behind the same IP. On 23 December 2019 2:18:35 AM NZDT, Damian <db76 at riseup.net> wrote: >Hello fellow mailing list readers, > >My question relates to multiple / duplicate connections to the ice cast