PDA

View Full Version : Transparent http Proxy Cache problem was Shoutcast pluginproblem



Kevin Hawkins
2004-04-19, 08:15
I have renamed this thread as really it's not a problem with the Shoutcast
plugin at all - and I felt it was misleading - it's a proxy server issue
with NTL broadband. I really like the Shoutcast plugin and this isn't a
problem with that plugin.

NTL apparently use several brands of proxy cache servers and also different
software revisions of each. Some show this problem and some dont.
Unfortunately they are enforced transparently and can only be bypassed if
your application allows for configuring a proxy cache manually.

Here's an easy example - using WinAMP set the proxy via WinAmp Preferences
to use 62.252.96.4:8080 (cache1-hudd.server.ntli.net) and then play Virgin
radio from http://64.236.34.196:80/stream/1031 and listen carefully - it has
a slight 1 second 'beat' over it and audio is slightly truncated - now if
you change the proxy cache to 62.254.64.4:8080 (cache1-midd.server.ntli.net)
and try again all is well. (Not sure if these proxies only work for NTL
customers). I believe you may have to restart WinAMP each time after
changing the proxy.

Now the difference in WinAmp is only minor, almost not noticeable, a
slight pulsing but via the SlimServer it is huge - I have no idea why this
should be as it makes the station totally unlistenable as in my sample at
http://www.ukusa.demon.co.uk/Example.mp3.

So it looks like I need to be able to configure a proxy cache in
SlimServer - or get NTL to get rid of /change the enforced transparent cache
on my broadband link. They say this is not possible and that they are not
intending to replace these anytime soon :-(

NTL Tech need to get a few other people who have this problem in
order to get NTL to investigate a solution so if this effects you let me
know. Otherwise I think the chances of a SlimServer feature to allow proxy
settings is far more likely to appear than moving that mountain that is
NTL....

K

PS Just got a return call from NTL who said they are going to forward the
problem report to their server people as 'clearly something is different'
between their cache servers operation if I can play WinAMP via one but not
the other. We'll see..... My local 'Huddersfield' area has 3 cache servers
available all of which exhibit the problem whereas the Middlesborough cache
listed above and the Cardif one at 62.252.32.7:8080 seem fine.

> -----Original Message-----
> From: discuss-bounces (AT) lists (DOT) slimdevices.com
> [mailto:discuss-bounces (AT) lists (DOT) slimdevices.com] On Behalf
> Of Kevin Hawkins
> Sent: 19 April 2004 12:10
> To: 'Slim Devices Discussion'
> Subject: [slim] Shoutcast plugin problem
>
> Ahhh - Just found these links as well..
>
> Assuming Simon has his setup working with NTL it would
> appear a way around this is to force a different type of
> proxy cache to be used by SlimServer - the 'inktomi' vs
> other brand. This I think would need a suitable
> configurable option available in SlimServer though wouldn't it ???
>
> http://homepage.ntlworld.com/robin.d.h.walker/cmtips/stream.html
>
>
> http://www.xinit.net/ntl/proxy.html
>
> Kevin
>

rtitmuss
2004-04-19, 12:53
Kevin,

Good detective work, it save me from unplugging my router. I have just tried
listen to Virgin radio using WinAMP and changing the proxy settings makes
all the difference for me as well. If you speak to NTL again then you can
let them know that at least one other person is effected by this.

I've just put together a small patch for the Slim Server to use a proxy
server for remote streaming, and am now listening to Virgin radio on my
squeezebox :-). I'll post the patch on the developers list and copy you in.

Regards,
Richard


----- Original Message -----
From: "Kevin Hawkins" <lists (AT) ukusa (DOT) demon.co.uk>
To: "'Slim Devices Discussion'" <discuss (AT) lists (DOT) slimdevices.com>
Sent: Monday, April 19, 2004 4:15 PM
Subject: [slim] Transparent http Proxy Cache problem was Shoutcast
pluginproblem


>
>
> I have renamed this thread as really it's not a problem with the Shoutcast
> plugin at all - and I felt it was misleading - it's a proxy server issue
> with NTL broadband. I really like the Shoutcast plugin and this isn't a
> problem with that plugin.
>
> NTL apparently use several brands of proxy cache servers and also
different
> software revisions of each. Some show this problem and some dont.
> Unfortunately they are enforced transparently and can only be bypassed if
> your application allows for configuring a proxy cache manually.
>
> Here's an easy example - using WinAMP set the proxy via WinAmp
Preferences
> to use 62.252.96.4:8080 (cache1-hudd.server.ntli.net) and then play Virgin
> radio from http://64.236.34.196:80/stream/1031 and listen carefully - it
has
> a slight 1 second 'beat' over it and audio is slightly truncated - now if
> you change the proxy cache to 62.254.64.4:8080
(cache1-midd.server.ntli.net)
> and try again all is well. (Not sure if these proxies only work for NTL
> customers). I believe you may have to restart WinAMP each time after
> changing the proxy.
>
> Now the difference in WinAmp is only minor, almost not noticeable, a
> slight pulsing but via the SlimServer it is huge - I have no idea why this
> should be as it makes the station totally unlistenable as in my sample at
> http://www.ukusa.demon.co.uk/Example.mp3.
>
> So it looks like I need to be able to configure a proxy cache in
> SlimServer - or get NTL to get rid of /change the enforced transparent
cache
> on my broadband link. They say this is not possible and that they are not
> intending to replace these anytime soon :-(
>
> NTL Tech need to get a few other people who have this problem in
> order to get NTL to investigate a solution so if this effects you let me
> know. Otherwise I think the chances of a SlimServer feature to allow proxy
> settings is far more likely to appear than moving that mountain that is
> NTL....
>
> K
>
> PS Just got a return call from NTL who said they are going to forward the
> problem report to their server people as 'clearly something is different'
> between their cache servers operation if I can play WinAMP via one but not
> the other. We'll see..... My local 'Huddersfield' area has 3 cache
servers
> available all of which exhibit the problem whereas the Middlesborough
cache
> listed above and the Cardif one at 62.252.32.7:8080 seem fine.
>
> > -----Original Message-----
> > From: discuss-bounces (AT) lists (DOT) slimdevices.com
> > [mailto:discuss-bounces (AT) lists (DOT) slimdevices.com] On Behalf
> > Of Kevin Hawkins
> > Sent: 19 April 2004 12:10
> > To: 'Slim Devices Discussion'
> > Subject: [slim] Shoutcast plugin problem
> >
> > Ahhh - Just found these links as well..
> >
> > Assuming Simon has his setup working with NTL it would
> > appear a way around this is to force a different type of
> > proxy cache to be used by SlimServer - the 'inktomi' vs
> > other brand. This I think would need a suitable
> > configurable option available in SlimServer though wouldn't it ???
> >
> > http://homepage.ntlworld.com/robin.d.h.walker/cmtips/stream.html
> >
> >
> > http://www.xinit.net/ntl/proxy.html
> >
> > Kevin
> >
>
>
>