What's new?

[stevewa2]

Hi, I was registered on this board back in 2016, but I could not remember which email address I used, so I could not reset my login password, so I created a 2nd user account.

I'm interested in getting back into online audio streaming, so I'm back to researching server software again, and came back to Steamcast.

I downloaded the latest Win version, dated Dec 2015, and wondered if you are still working on this project, or does it not need anything new since 2015?


I am interested in trying to use listener authentication triggers to recv listener data from http headers, and tie that in with some scripts (i.e. icecast url auth), which could be used to identify returning users, log visits, and play different intro files(i.e. "Hey welcome back [insert username here] !")

It appears the existing user auth is file based xml only, so I assume this idea is a no go?



Another question (not directly related to Steamcast):
Does anyone have a user auth stream that works with iOS radio stream listener apps such as "simple Radio"? How does an iOS (or Android) app handle an auth request? Does it redirect to a web browser on the smartphone to a url which user can login? I've never seen it.




I believe in your desire to make steamcast better than Icecast/Shoutcast, but I'm worried that it's been 4 years since a new version was released. And I'm not really clear on the advantages / benefits of using Steamcast instead of Icecast / Shoutcast or even Icecast-KH, which has source code available on GitHub if you want to extend the capabilities... If you want to describe what your vision for the future is, I'm all ears

[Jay]

We are not dead, but be aware this is a completely "for fun" project for us so we work on it as time permits so when other projects are putting food on the table this unfortunately puts this project on a bit of a back burner. I wish I had the funding to make it more but that's reality for you. That said, I have suddenly found myself with some time on my hands and I am interested in taking Steamcast further with the time I have. if you have ideas. pop them in here and I will see what I can do.

A big one for me will be HLS support as it is something I promised 2 years ago.

[stationx]

Hi Jay,

Would you mind looking over why the CPU gets sent to 100% after steamcast recieves an invalid incoming icy source..... I've posted it before..... I'm still struggling with it.

I've locked down all ports I can on my vps that steamcast runs on. It's Windows 2012 server r2..... To serve listeners on port 80 i'm running two instances of steamcast on the same vps with one on port 8100 and the other on port 80 ....i'm not using a proxy to do the work...... would a proxy be the better idea?

I was thinking it's because there is a lot of things crawlling port 80.... But i've seen the same thing happen on physical pc's running at the studio and on some other port like 8100 as mentioned above. Something comes along and steamcast sees it as an "incoming source" then regets it and some sort of issue then sends the cpu on the vps into a spin. There doesnt seem to be any difference between physical or vps machines...there is a massive amount of times it happens on the port 80 instances compared to the 8100 port.....

Regards
Pete

[Jay]

Interesting, I haven't noticed this on our Windows Server test instance (using port 80 as well), but to be clear, I haven't really been looking for it either. Do you have logs of the event that you believe is kicking off the CPU usage? Can you reproduce it yourself by sending requests to Source?

[stationx]

Hi Jay,

I'll see if i can get a log to you.
I setup a standalone version of the old edcast. I need to use it in shoutcast v1 mode and use the admin:password work around. As you know this means i'm coming in on port 81. This is part of my test process to see if the port is blocked by the vps external firewall. With this blocked it still happens. I also tried the idea of setting the SRCiP to 127.0.0.1 so it will only accept local inputs. I can't really tell if this worked but the issue still happens. I've banned IP's and have come to see repeat offenders "that are already banned". It's like they make it to the front door and then cause trouble in front of the server rejecting them. but whatever damage is already done, then it upsets everything inside even though the issue has gone away.
Would you mind letting me know if the scr ip and banning functions are working properly? I recall reading something that not everything was working fully..

Regards Pete

[Jay]

The "srcip" param works and only applies to the SHOUTcast v1 source port. So if someone is trying to make Icecast source connections on port 80, it wouldn't apply.

Banning should be working. If it isn't then it's definitely a bug that needs to be fixed, so logs of this would be great as well.

[stationx]

Hi Jay,

I have no idea how Steamcast works under the bonnet (just know it's one of the world's lesser known gems) and it works great! Apart from this little problem.. Would it be possible for this issue to cause dramas before it gets to the part of Steamcast that bans Users etc? That could be a clue too.

Since I've gotten your attention.... it's not happened.... still hoping for a chance to send you a log....

Regards Pete

[Jay]

No worries, just send over logs when it does, with everything that is going on in the world right now, I won't have a lot of distractions.

[stationx]

Hi Jay,

First chance to get a log to you since i got your attention. This is not on the port 80 instance. It's on the port 8000 one. When you scroll to the last entry you will se it comes in first asking for an invalid request. Then it says incoming icy. This is not always the case. Some are just the last one! I'll see what avails itself in then next few days. Please see below

Regards Pete

[04/18/2020@09:49:05] <www.steamcast.com> [/AirNews] ACK: Touch Successful. (tchfrq: 60)
[04/18/2020@09:49:21] <201.232.136.169> Connection Opened [U: Anonymous] (A: 103.1.184.7:8000/AirNews) [L: 3] {UA: VLC/3.0.8 LibVLC/3.0.8} [I: 26c7112a196c5c6a-26ce5671-47b4-5764-41426117cba0030de95bb06c]
[04/18/2020@09:49:24] <201.232.136.169> Connection Closed (Connection reset by peer) [U: Anonymous] [L: 2] {82938 bytes} (3 secs) [I: 26c7112a196c5c6a-26ce5671-47b4-5764-41426117cba0030de95bb06c]
[04/18/2020@09:49:35] <103.230.158.241> WEB REQ: 103.1.184.7:8000/admin/status.xml {UA: Mozilla/5.0 (Windows NT 6.3; rv:2.2.2.300) Radio Toolbox/2.2.2} |R: | [I: e1118a5ee1c3df5-969f8ed8-4eac-76d8-77431e625df5ab63a31b2100]
[04/18/2020@09:50:06] <www.steamcast.com> [/AirNews] ACK: Touch Successful. (tchfrq: 60)
[04/18/2020@09:50:14] <103.230.158.241> WEB REQ: 103.1.184.7:8000/admin/status.xml {UA: Mozilla/5.0 (Windows NT 6.3; rv:2.2.2.300) Radio Toolbox/2.2.2} |R: | [I: 45c3b0daf5df66cf-2fc9056f-48d8-6258-fe2509777208c5cc1bc6dd74]
[04/18/2020@09:50:28] <14.201.125.223> WEB REQ: 103.1.184.7:8000/admin.cgi {UA: (Mozilla Compatible)} |R: | [I: 7501978c6a8ca4c4-aec61d1a-4e68-6ef5-5d67beb3e44d01833b6fb08f]
[04/18/2020@09:50:53] <103.230.158.241> WEB REQ: 103.1.184.7:8000/admin/status.xml {UA: Mozilla/5.0 (Windows NT 6.3; rv:2.2.2.300) Radio Toolbox/2.2.2} |R: | [I: 14ef6b9a5dba32e3-33105c44-477f-4732-77cc962a6471245f10604776]
[04/18/2020@09:51:07] <www.steamcast.com> [/AirNews] ACK: Touch Successful. (tchfrq: 60)
[04/18/2020@09:51:33] <103.230.158.241> WEB REQ: 103.1.184.7:8000/admin/status.xml {UA: Mozilla/5.0 (Windows NT 6.3; rv:2.2.2.300) Radio Toolbox/2.2.2} |R: | [I: 98980fac8aa894ec-37bffa03-4213-4e37-43b2d77a58743f0bc5bbc95c]
[04/18/2020@09:52:08] <www.steamcast.com> [/AirNews] ACK: Touch Successful. (tchfrq: 60)
[04/18/2020@09:52:12] <103.230.158.241> WEB REQ: 103.1.184.7:8000/admin/status.xml {UA: Mozilla/5.0 (Windows NT 6.3; rv:2.2.2.300) Radio Toolbox/2.2.2} |R: | [I: de6c715ffc6c0125-73b25cbf-4927-4dde-153e356881f0eee5ca508122]
[04/18/2020@09:52:26] <dir.xiph.org> [/AirNews] ACK: Updated server info. (tchfrq: 242)
[04/18/2020@09:52:55] <103.230.158.241> WEB REQ: 103.1.184.7:8000/admin/status.xml {UA: Mozilla/5.0 (Windows NT 6.3; rv:2.2.2.300) Radio Toolbox/2.2.2} |R: | [I: 79e7974dceb6a7bd-2025cb28-4d08-4bad-4397a04382fbec4c12e7eac1]
[04/18/2020@09:53:09] <www.steamcast.com> [/AirNews] ACK: Touch Successful. (tchfrq: 60)
[04/18/2020@09:53:13] <62.210.113.236> Invalid Resource Request (/manager/html) {UA: User-Agent:Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.2; .NET CLR 1.0.3705}
[04/18/2020@09:53:14] <62.210.113.236> Incoming ICY Source

[stationx]

Hi Jay,

I run a separate box for a couple of mates. This is not the one that gets hit the most (normally) that would be my main box. But for some reason this is the only one giving me what I need, so you can see it. Everything has been ok over on the main box. Which as you would imagine sees a lot more hits and therefor more chances for issues.

You should see straight away that in this instance it simply appears as an incoming source. There is no "invalid resource request" first. This is what I see the most..... Just the incoming icy..... Then it sets the vps' CPU to flat out.

Cheers Buddy Pete

[04/22/2020@14:52:58] <103.230.158.241> WEB REQ: 103.1.184.7:8000/admin/status.xml {UA: Mozilla/5.0 (Windows NT 6.3; rv:2.2.2.300) Radio Toolbox/2.2.2} |R: | [I: 604041b4481f7838-bd1f9b6d-4eb3-4594-998b8f9bf3743bf410a763ca]
[04/22/2020@14:53:02] <www.steamcast.com> [/AirNews] ACK: Touch Successful. (tchfrq: 60)
[04/22/2020@14:53:36] <103.230.158.241> WEB REQ: 103.1.184.7:8000/admin/status.xml {UA: Mozilla/5.0 (Windows NT 6.3; rv:2.2.2.300) Radio Toolbox/2.2.2} |R: | [I: f79fcb77958d23c8-f95d0436-435e-5dca-76ee2d6aeb562e3f25e83920]
[04/22/2020@14:53:38] <dir.xiph.org> [/AirNews] ACK: Updated server info. (tchfrq: 242)
[04/22/2020@14:54:03] <www.steamcast.com> [/AirNews] ACK: Touch Successful. (tchfrq: 60)
[04/22/2020@14:54:14] <103.230.158.241> WEB REQ: 103.1.184.7:8000/admin/status.xml {UA: Mozilla/5.0 (Windows NT 6.3; rv:2.2.2.300) Radio Toolbox/2.2.2} |R: | [I: f8c32fc279e77d5a-c773d91b-485c-5e86-b61dce566f4e44336ed5541b]
[04/22/2020@14:54:50] <103.230.158.241> WEB REQ: 103.1.184.7:8000/admin/status.xml {UA: Mozilla/5.0 (Windows NT 6.3; rv:2.2.2.300) Radio Toolbox/2.2.2} |R: | [I: 32b568e7a73df8f4-700ab89a-4e29-65f6-e36e413e157d7a8b42aae5e4]
[04/22/2020@14:55:04] <www.steamcast.com> [/AirNews] ACK: Touch Successful. (tchfrq: 60)
[04/22/2020@14:55:06] <89.40.73.234> Incoming ICY Source

[Max]

Hi,

So these IPs that is generating the Incoming ICY Source is causing the high CPU usage, correct? I'm thinking they're bots probably spamming various things. I will check the code to make sure that invalid ICY sources get dumped immediately.

If possible a packet capture of these requests would be very helpful.

[stationx]

Hi Max...

Yes buddy. I did think "bot" myself as this "usually" effects the "port 80" instance of Steamcast only. I was thinking some sort of google page crawling bot that was unique to port 80. But then a few started on other ports and is no longer the case. I use various ports instead of the normal port 8000.... It doesn't seem to matterif it's on 8000 or something like 8100 they seem to find it. But the main offender is truly port 80.

Sorry i'm not sure what you mean by "packet capture".
Regards
Pete

[Max]

What OS and version of OS are you running Steamcast on (Windows 10/Ubuntu 18.04)?

For packet captures on Windows, to do them you'd need Wireshark.

For Linux you can use something like tshark or tcpdump.

[stationx]

Hi Max

Windows Server 2012 R2 - These are VPS in case that makes a difference.

Looks like I need wireshark......

Thanks for getting onto this. Regards Peter

[Max]

Hi,

Also, once you get the packet capture please just PM it to me. This is for privacy as it may catch things that shouldn't be shared publicly.