Latency problem - but not like you are expecting (i hope)

[djmx2006]

I have used shoutcast to broadcast for many years now as a DJ and running the shoutcast server. But I have run into a problem that has confused me completely.

I have a server configured (shoutcast 1 not 2) and am able to broadcast to it fine on a specified port 8000 for example.

I (or someone else) then try and listen back to my stream and get a huge buffer which never seems to complete.

The server is running Centos 6.2 with plenty of bandwidth, There is a firewall/router in between it and the outside world (potential problem), and then internet connection to me.

From shoutcast I connect and see data passing from the DSP to the server at normal speed for a 128k stream.

Correct me if I am wrong but as I understand when a listener connects on the main port (8000 for example), the sound is then streamed back to them on 8001 (i.e. port + 1)? That is all enabled in my firewall and data does get to my player as far as I can tell (just very slowly causing the huge buffer).

I accept this is most likely to be a network problem, but from a server end is there anything I can look at to see that the data is actually sending to the client at a normal speed? If so then that eliminates it to being server config, and points towards firewall.

I am just looking for pointers for how to narrow down the issue if anyone can help

[DrO]

Correct me if I am wrong but as I understand when a listener connects on the main port (8000 for example), the sound is then streamed back to them on 8001 (i.e. port + 1)? That is all enabled in my firewall and data does get to my player as far as I can tell (just very slowly causing the huge buffer).

8001 is only used for _source_ connections and not client connections. client connections are always provided on the main 'portbase'

I accept this is most likely to be a network problem, but from a server end is there anything I can look at to see that the data is actually sending to the client at a normal speed? If so then that eliminates it to being server config, and points towards firewall.

people have used network monitoring tools to see what is going on (cannot remember any that have been explicitly used) to determine the networking load / rate coming out of the DNAS (there's nothing natively built into the DNAS in either version to do such things).

though some routers people have found have issues when doing loop back connections like you're describing you are attempting for testing the server connection.

-daz

[djmx2006]

Thanks for your first comment, yes I got it wrong way around and its broadcaster that uses 8001 to stream.

How do you mean by a loopback connection? And what sort of issues have they had? Similar to what im describing?

[DrO]

How do you mean by a loopback connection?

it's when the connection is sent striaght back by the router without it making it outside of the LAN.

And what sort of issues have they had? Similar to what im describing?

pretty much the same sort of thing with connections not behaving in the manner expected.

really without being able to try the stream out, it's all just guessing as it could be doing the same for everyone else due to some specific aspect of your setup.

-daz