connection rejected. Bad icy header string [icy-name:]

[DrO]

rightio, that would make sense then since there's generally meant to be an url specified as the v2 DNAS is more strict in following that requirement so i may need to lessen it to improve legacy compatibility and just force it to a default url - though if you've got things working now then that shouldn't be too much off an issue (but will have a think about it).

-daz

[rcweb]

Has this been resolved?

I am using B.U.T.T. and am also still getting the "connection rejected" in the DNAS logs on my server.

[DrO]

a build with the fix in it has not been publically released.

-daz

[radbatik]

DrO: I'm seeing this same issue and I'm wondering if there is an idea of when this will be publicly available. I'd also like to get a copy of the build with this fix, if you could provide it.

Thanks!

Edit: I neglected to mention that this is running in a Windows 64-bit environment.

[sirmonkey]

twice in a day...
have this fix for this been released yet?
2013-01-27 15:05:44 I msg:[SRC 192.168.1.6:57370 sid=1] SHOUTcast 1 source connection.
2013-01-27 15:05:44 E msg:[SRC 192.168.1.6:57370 sid=1] connection rejected. Bad icy header string [icy-name:]

I have a client that uses B.U.T.T. and some shitty instreamer bentix? thing ( i'm probably going to build a mini-itx or rase PI box to replace it once i get this shoutcast stuff figured out)

If its not publicly aviable, can i get the recent build? or someting? i'm running the linux shoutcast server package.

Thanks.


ps if it has been fixed. a screen shot of a working B.U.T.T. config would be a good idea ;-) i screen shot everything now adays.

[DrO]

there is no new public build with the fix available and i'm not giving out test builds for an issue which i know is already confirmed as fixed.

-daz

[Daniel Nöthen]

Hello guys,

butt development has been reactivated for a short amount of time and
finally I'm happy to tell you that the bug has been fixed in butt 0.1.13.
The icy strings are now sent at once and every empty icy field is filled with a "none".
That seems to make the DNAS v2 happy!

More at:

https://sourceforge.net/p/butt/news/

Daniel

[DrO]

it wasn't needed anymore as the DNAS had been updated to support things like butt was doing (which wasn't the only one doing it). and its better to leave fields blank instead of set as 'none' as that's more likely to pollute the SHOUTcast system with pointless information.

[Daniel Nöthen]

Well, I tested it with butt 0.1.12 and SHOUTcast DNAS/posix(linux x64) v2.2.1.109 (Nov 29 2013). It did not work. Also, leaving fields blank printed me errors. I can't remember exactly which, but filling the fields with contents, solved it. I'm sorry, that this possibly pollutes the SHOUTcast system

[Daniel Nöthen]

I just verified what the problem has been.
The DNAS v2 doesn't like fields to be empty, but it allows that fields are not transmitted at all.
Not transmitting every icy header breaks the DNAS v1, though. On DNAS v1 empty fields seem to be accepted. So, filling every field was the only way to be compatible to both DNAS versions.

If you would provide me a DNAS v1 protocol description that is verified to work on DNAS v1 and v2, I will implement it the correct way. Or is there already one that I just could not find on the web?

[DrO]

I don't have access to the v2 source code currently, but I'm sure I'd set it so as long as a name was specified it should work (though a genre is best provided otherwise it defaults to misc which is of no use to anyone). and the v2 DNAS should report what is missing.

the v1 DNAS is not supported (especially since the ownership change) and I don't have the means to check what it supports or not (I can't remember anyway) so is up to you how much you want to set, but anything deemed too generic when a stream is attempting to be listed will often cause the stream not to be listed.