[Icecast] Icecast behind a Router
geoff at hitsandpieces.net
Fri Mar 18 22:30:02 PST 2005
Here's why binding to various interfaces can trap you. It's really only
necessary to do this if you want icecast *not* to listen to a particular
For example: I route using my primary Linux box, which has two network
cards in it. So this box has the following addresses:
Internet address: 188.8.131.52
LAN address: 10.2.0.1
Local loopback: 127.0.0.1
Now, if I bind Icecast to listen to my Internet address, then if I try to
connnect to it directly over the LAN or from the local host using
127.0.0.1, it's not going to work as Icecast is only listening on one
interface. So unless you specifically want to prevent connnections for a
given interface, you may as well leave the bind stuff alone.
Now, you could of course bind it to your LAN address to prevent people on
the net from tuning in, and you could in theory have one server on your LAN
and another on your Internet interface (you can even set up separate ports
on the same server this way). But these cases are probably the exception
rather than the rule.
Geoff Shang <geoff at hitsandpieces.net>
MSN: geoff at acbradio.org
Make sure your E-mail can be read by everyone!
Please avoid sending me Word or PowerPoint attachments.
More information about the Icecast