Bind Shoutcast2 to multiple ports
 

Is it possible to bind shoutcast2 to multiple ports. Due to firewall issues on some smartphone providers we're forced to be visible behind port 80 and 8100. Is this possible using 1 instance of shoutcast2? Or do we need (just like v1) two seperate instances to be startup?

Kind regards,
Vincent Bruijnes

the v2 DNAS only needs one port to be able to serve up the multiple streams it is able to support i.e. port 80 or 8100, but definitely not a separate port per stream. you can also run it in the same manner as a v1 DNAS with one instance per stream i.e. #1 is on port 80 and #2 is on port 8100.

-daz

Hmmm, that's not the answer I was hoping for. That leaves us creating double configurations per server. Is there a way like icecast to tell a "leaf" server to relay all instances/streams on the primary at once?

from the sounds of it you're already doing double configurations - i'm not aware of the 'leaf server' term from icecast though i guess it's a way to specifically provide a relay server to use?

if that is the case, then at the moment there's no way to tell the DNAS a backup url to use (though is eventually going to come - i've no eta when as i'm not working on the DNAS itself for the time being). if it is listed publically and the main instance is set to a low client number then it will auto-direct to the backup instance where possible.


however, what i'm not getting is why you need to have things on port 80 and 8100, as being on just port 80 should allow things through and to work without issues even in a firewalled setup.

-daz

Don't ask me why, but some mobile operators in holland block mp3 streaming on servers running shoutcast on port 80. I have tested it changing the port to 8100 and suddenly it works. Anyway, what I meant was a way that all configuration can be 'synced' between servers. This to avoid having to configure 2 (or more) servers.

hmm, well if using a common 'base' config file then that is about the way to do it as things are (since i don't see things being changed to pass configs between servers automatically) and then have any specific config files including the base config. since really how often are you going to need to keep tinkering with the config files anyway?

-daz