similar to: IPV6 in version 2.4.4

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

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

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>

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

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

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

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:

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

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

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

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

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

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

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

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). ? > > > >

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

Hi, I realise that the web is littered with posts and discussions concerning the topic of getting icecast stats from the xsl files (status-son.xsl) in the icecast web directory. As you may know, many of the solutions are outdated and example links are broken. I have limited knowledge of how to write my own javascript to get this info to display on my own website. Wondering if anyone can refer me

Hi, I apologise for the naiveness of this question, but I experienced an error when running apt-get update on Debian 9. It’s telling me that it can’t update the xiph repository. Not sure if I should be asking for help about this here, but if not… please let me know where I should take this issue. Any help is appreciated. Damian Get:1 http://security.debian.org/debian-security stretch/updates