Hi all,

I have just moved my slimserver to a fedora box and am going through the
woes of installing AlienBBC
Follwing the troubleshooting, the 5123:RealAudio.... Example works fine
from a local browser
Opening a remote winamp and trying to connet to a standalone
transcoder_proxy doesn't work
Seems that the proxy retrieves the MRL and starts buffering it

Then the following appears:

Writing Bytes to <client address>:<port>
Writing Bytes to <client address>:<port>
Socket (<client address>:<port>) Gone away!
Closing Down <client address>:<port>
After a few clean up lines it starts trying again.
The port changes: 3744, 3761, etc.

At first I thought that this was a firewall issue, but I stopped
iptables and the same behaviour.

Any suggestions..


-----Original Message-----
From: discuss-bounces (AT) lists (DOT) slimdevices.com
[mailto:discuss-bounces (AT) lists (DOT) slimdevices.com] On Behalf Of
robin-lists (AT) robinbowes (DOT) com
Sent: Monday, October 04, 2004 9:01 PM
To: 'Slim Devices Discussion'
Subject: [slim] AlienBBC on Fedora

Hi all,

I've just got AlienBBC running on my Fedora Core 2 box and thought I'd
share a
couple of issues I ran into (and recommend that the AlienBBC
documentation is

1. Open the firewall
Open port 5123:tcp in Iptables. I use system-config-security-tui to
the firewall ports - I'm sure there are many other ways to do this.
(You will of course already have ports 3483:tcp, 3483:udp and 9000:tcp
opened to
allow connections to slimserver)

2. Set the location of lame correctly
On my Fedora installation, lame is installed in /usr/bin (rather than
/usr/local/bin as specified by default in trancoder_proxy.pl.
Set the location of the lame executable correctly in the $mp3_encoder
(line 15 in v0.9).

Now that I've done this it's working like a charm!

Top job Jules!