search for: 2_3_3

...ts "fighting" >> for the mount and _both_ updating the metadata. This was disabled by >> only allowing metadata updates from the same IP as the source client. > At what point did this change occur? As this may be related partially... http://icecast.org/news/icecast-release-2_3_3/ "Only allow raw metadata updates from same IP as connected source (unless user is admin). This addresses broken client software that issues updates without being connected." > I develop on one system which is definitely a different IP than the > source... BUT as I recall, I'...

...emember if we change log verbosity on a reload. >> Surely you do have a test environment that you could use for your >> testing purposes? > I can setup a VM with a test server in it, but if I have the coders I ask > them. > > >> http://icecast.org/news/icecast-release-2_3_3/ >> "Only allow raw metadata updates from same IP as connected source >> (unless user is admin). This addresses broken client software that >> issues updates without being connected." >> If you use 2.3.3, then using admin credentials is your only option to >>...