Re: slimserver and firewall

On Tuesday 31 January 2006 12:32, Gerhard Magnus wrote:
> Hello All,
>
> I'm trying to understand how the client/server interacts with
> ports and firewalls by exploring a non-essential application on
> my home network. The boxes are running FC4 and are connected to a
> router behind a DSL modem.
> The application is slimserver which streams mp3 files over a
> network to a piece of hardware called a Squeezebox Network Music
> Player, which I don't have. It can also steam the same files
> over the Internet to an mp3 player like xmms running anywhere on
> the network, which is how I want to use it.
> The documentation says that slimserver (which I have installed
> on one machine) must be reachable via port 9000. I program the
> slimserver playlist (which can include Internet radio) at
> http://localhost:9000. The clients (xmms) access the stream at
> http://localhost:9000/stream.mp3, where "localhost" is now the
> name of the box where slimserver is running. So far I can play
> music on the server machine but not remotely.

"localhost" is somewhat synonymous with "the machine you're sitting
in front of" so if you're trying to connect using "localhost" the
only machine that will work is "the one you're sitting in front
of". To connect over the network you'll have to know the IP
address of the server; i.e. http://192.168.1.1:9000/stream.mp3.

For this to work, you'll have to make sure that your machine running
the slimserver program has port 9000 available to the other
machines on your network. A quick test is to just turn off your
iptables firewall if you have it running; i.e.
"/etc/init.d/iptables stop" from a console prompt on the machine
with the slimserver program. If you want to re-enable a firewall
there are several applications that will make configuring a
firewall easier; e.g 'webmin'.

For machines on the Internet to connect to your slimserver machine
you'll have to configure your router to forward port 9000 to your
machine running the slimserver program. How this is done will vary
on the kind of router you are using.

Setting this up may require you to learn how to troubleshoot network
connections. Learning to use ping. netstat, tcpdump, iptraf, nmap,
etc. won't be a waste of time.


Regards, Mike Klinke

--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

Relevant Pages

  • Re: Turning on Media Sharing in WMP11
    ... I believe it forms quite a reasonable network media device. ... Turning on SSDP (it was disabled as was uPnP) to Manual and then UPnP ... If there is a firewall, or NAT, built into your ... You need to open port s: ...
    (microsoft.public.windowsmedia.player)
  • Re: Identifying Internet Attacks
    ... contain the hacker to a particular machine, leave the machine on the network ... Some firewall software such as ... open ports; however, this will not identify which program is using the port. ... firewall logs, the IIS web and ftp server logs and Windows security event ...
    (microsoft.public.inetserver.iis.security)
  • Re: Leopard Firewall Warning
    ... machines on a particular network can access a port. ... The new scheme is an XP-style application based firewall; ... This, as an example, allows an attacker, once ...
    (uk.comp.sys.mac)
  • Re: firewall ports
    ... > I am wondering how safe my network is with the firewall i have set up.. ... how does this compromise the security to my network if at all? ... non-standard ports, anyone can run nmap or any type of port scanner to see ...
    (comp.security.firewalls)
  • Re: Port 21 open on pcs not running ftp?
    ... All of the pcs are on the local network, ... firewalls in place are the windows xp firewall included in sp2. ... that the open port doesn't appear locally. ... Our network switches are Dell powerconnect gigabit switches which ...
    (microsoft.public.security)