Re: more on thedj.com

Recently, Brian talked about "Re: more on thedj.com", and said
>
> On Tue, 24 Feb 1998, Michael Pelletier wrote:
>
> > On Tue, 24 Feb 1998, Brian wrote:
> > > >
> > > > TheDJ uses RealAudio, which requires their own proprietary proxy.
> > > > No, it will not work with Squid, and never will until RealAudio
> > > > is willing to release the details of their data stream. You will
> > > > need to purchase a copy of the RealAudio proxy if you wish to
> > > > allow your users to stream audio through your network.
> > >
> > > But realaudio doesnt use port 80, and I only proxy port 80. So shouldnt
> > > that data just go right thru?
> >
> > New versions of RealAudio can use HTTP to request RA clips from sites, but
> > the RealAudio application-layer proxy operates on port 1090. It was built
> > using the TIS firewall toolkit, and is freely distributable. Since it
> > sounds like what you're saying is that you have full routing out to the
> > internet, it sounds like you should just turn off proxy functionality for
> > theDJ player. No?
>
> Thats the thing. Using the dj player, with proxy turned off in the dj
> player, it still doesnt work. DJ player sends requests to port 80, which
> get transparently redirected to port 2138 of the squid. And it doesnt
> work. Everything else has always worked fine, I just don't know what is
> so special about this dj program that it breaks with squid.

I believe that is because the query on port 80 that is sent
to the server triggers a response on a *different* port (port
1090, it would seem according to Mike) with the RA stream.
With Squid in the way, the client IP that is making the
connection is the Squid proxy, NOT the actual person
sitting at their browser. So, the audio stream that is
sent back from the RA server hits the Squid box, and
cannot find an instance of a RealAudio Player to accept
the audio stream, and then aborts. The RA proxy would
handle the work of taking the audio stream and forwarding
it back across to the real requestor. It won't do any
caching, so you wouldn't be saving any bandwidth, but
at least it would allow your users to continue functioning.

The "special" part of the dj program is that it's sending
the response back on a different port, one that Squid doesn't
listen to, and it sends it back to the IP of the far end of
the socket that was opened to the server. :-(
 
> > > -Mike
> Pelletier. >
>
> /-------------------------- signal@shreve.net -----------------------------\
> | Brian Feeny | USR TC Hubs | ShreveNet Inc. (318)222-2638 |
> | Network Administrator | Perl, Linux | Web hosting, online stores, |
> | ShreveNet Inc. | USR Pilot | Dial-Up 14.4-56k, ISDN & LANs |
> | 89 CRX DX w/MPFI, lots of |-=*:Quake:*=-| http://www.shreve.net/ |
> | mods/Homepage coming soon |LordSignal/SN| Quake server: 208.206.76.47 |
> \-------------------------- 318-222-2638 x109 -----------------------------/

Matt

-- 
InterNex Information Services   |           Matthew Petach {MP59}
Senior Network Engineer         |           mpetach@internex.net
2306 Walsh Avenue               |           Tel: (408) 327-2211
Santa Clara, CA  95051          |           Fax: (408) 496-5484