suggestion

"Yaniv Sharon" <[email protected]> Sun, 20 Dec 2015 12:15:01 +0200
Newsgroups gmane.comp.audio.icecast.devel
Message-ID <[email protected]>
Hi all!

Please look at the log and I will describe bellow. 


[2015-12-16  14:42:44] INFO source/source.c listener count on /stream1 now
215
[2015-12-16  14:42:45] INFO source/source.c listener count on /stream1 now
214
[2015-12-16  14:42:53] INFO source/source.c listener count on /stream1 now
215
[2015-12-16  14:42:54] INFO source/source.c listener count on /stream1 now
214
[2015-12-16  14:43:00] INFO source/source.c Client 79355 (112.213.89.X) has
fallen too far behind, removing
[2015-12-16  14:43:00] INFO source/source.c listener count on /stream1 now
213
[2015-12-16  14:43:04] INFO source/source.c listener count on /stream1 now
214
[2015-12-16  14:43:05] INFO source/source.c listener count on /stream1 now
213
[2015-12-16  14:43:06] INFO source/source.c Client 79236 (112.213.89.X) has
fallen too far behind, removing
[2015-12-16  14:43:06] INFO source/source.c listener count on /stream1 now
212
[2015-12-16  14:43:09] INFO source/source.c Client 79245 (112.213.89.X) has
fallen too far behind, removing
[2015-12-16  14:43:09] INFO source/source.c listener count on /stream1 now
211
[2015-12-16  14:43:13] INFO source/source.c listener count on /stream1 now
212
[2015-12-16  14:43:14] INFO source/source.c listener count on /stream1 now
211
[2015-12-16  14:43:17] INFO source/source.c Client 79193 (112.213.89.X) has
fallen too far behind, removing
[2015-12-16  14:43:17] INFO source/source.c listener count on /stream1 now
210
[2015-12-16  14:43:22] INFO source/source.c listener count on /stream1 now
211
[2015-12-16  14:43:24] INFO source/source.c listener count on /stream1 now
212
[2015-12-16  14:43:24] INFO source/source.c listener count on /stream1 now
213
[2015-12-16  14:43:24] INFO source/source.c listener count on /stream1 now
212
[2015-12-16  14:43:25] INFO source/source.c listener count on /stream1 now
211
[2015-12-16  14:43:25] INFO source/source.c Client 79278 (112.213.89.X) has
fallen too far behind, removing
[2015-12-16  14:43:25] INFO source/source.c listener count on /stream1 now
210
[2015-12-16  14:43:26] INFO source/source.c listener count on /stream1 now
211
[2015-12-16  14:43:33] INFO source/source.c listener count on /stream1 now
212
[2015-12-16  14:43:33] INFO source/source.c listener count on /stream1 now
213
[2015-12-16  14:43:34] INFO source/source.c listener count on /stream1 now
212
[2015-12-16  14:43:36] INFO source/source.c listener count on /stream1 now
213
[2015-12-16  14:43:37] INFO source/source.c listener count on /stream1 now
212
[2015-12-16  14:43:37] INFO source/source.c listener count on /stream1 now
213
[2015-12-16  14:43:37] INFO source/source.c listener count on /stream1 now
212
[2015-12-16  14:43:44] INFO source/source.c listener count on /stream1 now
213
[2015-12-16  14:43:45] INFO source/source.c listener count on /stream1 now
212
[2015-12-16  14:43:48] INFO source/source.c listener count on /stream1 now
213
[2015-12-16  14:43:48] INFO source/source.c listener count on /stream1 now
191
[2015-12-16  14:43:49] INFO source/source.c listener count on /stream1 now
190
[2015-12-16  14:43:54] INFO source/source.c listener count on /stream1 now
191
[2015-12-16  14:43:54] INFO source/source.c listener count on /stream1 now
190

All what happened is related to one listener (112.213.89.X)
He was connected like 22 "true listeners" (213 - 191) for almost 15min (a
"true listeners" because the outgoing bandwidth
from the server was increased / decreased respectively and in one shot at
the disconnection, same in the ice listener count).
From time to time case like that happens. once in a week or two. I don't
know
If it's kind of attack or innocent listener with bad luck.

Because I'm pretty sure that there is a several connections to/from the
client during
The process of connecting to the stream and listening, things that over my
knowledge,
I CARFULLY suggest that IF the ice "derived" into situation that he
providing the stream
more than X times to the same ip for X time, SO he will auto kick&ban the
listener for X time.

or any other solution that you can think that will prevent kind of situation
like that. :-)

Yaniv.