I use a few raspberry pi’s and leave the icecast settings as localhost, and run darkice on the same Pi, I have let the router know to pass requests to port 8000 to the IP of the Pi. Using your external IP is not right, if your server is say 192.168.1.21 thats the port forward, just be sure that the ports you use are in the router too, udp/tcp I use both myself watch for typos. I think you are looking into it too far, its basic really, sometimes I find rebooting the router (depends on type) will open the ports after a config change within the router, find its system settings in router, and use the reboot option if you can find it, else a cold boot – switch it off for 30sec. Regards From: Damien Sykes-Lindley Sent: Friday, July 22, 2016 9:54 PM To: Icecast streaming server user discussions Subject: Re: [Icecast] Config and other areas of struggle Hi Alan, In actual fact, I’m having to test everything (server, streamer and player) on the same machine, which is configured in my router to be the server. I have opened the port specified in my config and the port after it and I have set it to allow both TCP and UDP, as I didn’t know which it used. I have also tried setting the hostname to my external IP address rather than a domain, and have even tried linking the port to a bound address, nothing. In fact if I specify a bind-address it actually comes up with an error when starting the server itself. Cheers. Damien. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.xiph.org/pipermail/icecast/attachments/20160722/08eeaa25/attachment.html>
Hi Alan,
Icecast set up is almost too easy:
heres the checklist
Give your server a fixed IP In Windows this is easy and there are plenty
of help files.
Make sure you get the DNS number right. Various modem routers default to
192.168.1.1 or 192.168.1.254 or variants of 10.x.x.x
in a console [ black screen with c:> under accessories] type ipconfig
<enter> to see what you have now.
On your router set up port fowarding so the outside world connects to
your router on x.x.x.x and port 8000 is fowarded to the fixed IP of your
server.
You can get in to your router by typing 192.168.1.1 [or whatever it is]
in a browser and the username admin password admin for 99% of the time.
Configure icecast.xml as below; this is from a linux server but
basically it's the same
<icecast>
<!-- location and admin are two arbitrary strings that are e.g. visible
on the server info page of the icecast web interface
(server_version.xsl). -->
<location>putsomethinginhere</location>
<admin>youremail at somewhere/admin>
<limits>
<clients>100</clients> <--- note increases on defaults
<sources>20</sources>
<threadpool>15</threadpool>
<queue-size>524288</queue-size>
<client-timeout>30</client-timeout>
<header-timeout>15</header-timeout>
<source-timeout>10</source-timeout>
<!-- If enabled, this will provide a burst of data when a client
first connects, thereby significantly reducing the startup
time for listeners that do substantial buffering. However,
it also significantly increases latency between the source
client and listening client. For low-latency setups, you
might want to disable this. -->
<burst-on-connect>1</burst-on-connect>
<!-- same as burst-on-connect, but this allows for being more
specific on how much to burst. Most people won't need to
change from the default 64k. Applies to all mountpoints -->
<burst-size>65535</burst-size>
</limits>
<authentication>
<!-- Sources log in with username 'source' -->
<source-password>somepassword</source-password>
<!-- Relays log in username 'relay' -->
<relay-password>somepassword</relay-password>
<!-- Admin logs in with the username given below -->
<admin-user>admin</admin-user>
<admin-password>somepassword</admin-password>
</authentication>
<!-- set the mountpoint for a shoutcast source to use, the default if
not
specified is /stream but you can change it here if an alternative is
wanted or an extension is required
<shoutcast-mount>/live.nsv</shoutcast-mount>
-->
<!-- Uncomment this if you want directory listings -->
<!--
<directory>
<yp-url-timeout>15</yp-url-timeout>
<yp-url>http://dir.xiph.org/cgi-bin/yp-cgi</yp-url>
</directory>
-->
<!-- This is the hostname other people will use to connect to your
server.
It affects mainly the urls generated by Icecast for playlists and yp
listings. -->
<hostname>192.168.0.30</hostname> <-- this is where you
put the server "name"
<!-- You may have multiple <listener> elements -->
<listen-socket>
<port>8000</port>
<!-- <bind-address>127.0.0.1</bind-address> -->
<-- the <!-- and --> comment the line out
<!-- <shoutcast-mount>/stream</shoutcast-mount> -->
</listen-socket>
<listen-socket>
<port>8004</port>
</listen-socket>
<!--<master-server>127.0.0.1</master-server>-->
<!--<master-server-port>8001</master-server-port>-->
<!--<master-update-interval>120</master-update-interval>-->
<!--<master-password>hackme</master-password>-->
<!-- setting this makes all relays on-demand unless overridden, this is
useful for master relays which do not have <relay> definitions
here.
The default is 0 -->
<!--<relays-on-demand>1</relays-on-demand>-->
<!--
<relay>
<server>127.0.0.1</server>
<port>8001</port>
<mount>/example.ogg</mount>
<local-mount>/different.ogg</local-mount>
<on-demand>0</on-demand>
<relay-shoutcast-metadata>0</relay-shoutcast-metadata>
</relay>
-->
<!-- Only define a <mount> section if you want to use advanced
options,
like alternative usernames or passwords -->
<!-- <mount>
<mount-name>/thewirelessstation.mp3</mount-name> <--
ignore this and leave defaults. I have this set up for something.
<username>someuser</username>
<password>somepassword</password>
<max-listeners>100</max-listeners>
<burst-size>65536</burst-size>
<stream-name>The Wireless Station 1530kHz Hawkes
Bay</stream-name>
<stream-description>The best music you ever will
hear</stream-description>
</mount>
-->
<fileserve>1</fileserve>
<paths>
<!-- basedir is only used if chroot is enabled -->
<basedir>/usr/share/icecast2</basedir>
<!-- Note that if <chroot> is turned on below, these paths
must both
be relative to the new root, not the original root -->
<logdir>/var/log/icecast2</logdir>
<webroot>/usr/share/icecast2/web</webroot>
<adminroot>/usr/share/icecast2/admin</adminroot>
<!-- <pidfile>/usr/share/icecast2/icecast.pid</pidfile>
-->
<!-- Aliases: treat requests for 'source' path as being for
'dest' path
May be made specific to a port or bound address using the
"port"
and "bind-address" attributes.
-->
<!--
<alias source="/foo" destination="/bar"/>
-->
<!-- Aliases: can also be used for simple redirections as well,
this example will redirect all requests for http://server:port/ to
the status page
-->
<alias source="/" destination="/status.xsl"/>
</paths>
<logging>
<accesslog>access.log</accesslog>
<errorlog>error.log</errorlog>
<!-- <playlistlog>playlist.log</playlistlog> -->
<loglevel>3</loglevel> <!-- 4 Debug, 3 Info, 2 Warn, 1
Error -->
<logsize>10000</logsize> <!-- Max size of a logfile
-->
<!-- If logarchive is enabled (1), then when logsize is reached
the logfile will be moved to
[error|access|playlist].log.DATESTAMP,
otherwise it will be moved to [error|access|playlist].log.old.
Default is non-archive mode (i.e. overwrite)
-->
<!-- <logarchive>1</logarchive> -->
</logging>
<security> <-- not sure what happens in windows but the
default will work
<chroot>0</chroot>
<!--
<changeowner>
<user>nobody</user>
<group>nogroup</group>
</changeowner>
-->
</security>
</icecast>
This should help
regards
Robert
--
*Communication Consultants*
64 Warner Park Avenue
Laingholm
Auckland 0604
09 8176358
0221693124
06 650 6087
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.xiph.org/pipermail/icecast/attachments/20160723/174f643e/attachment-0001.html>
On 22 Jul 2016, at 23:12, Alan Bowness wrote:> I use a few raspberry pi’s and leave the icecast settings as > localhost, and run darkice on the same Pi, I have let the router know > to pass requests to port 8000 to the IP of the Pi. > Using your external IP is not right, if your server is say > 192.168.1.21 thats the port forward, just be sure that the ports you > use are in the router too, udp/tcp I use both myself watch for typos.The hostname should be set to the external hostname of the server, NOT the internal IP (like 192.168.x.x) unless you only use Icecast in your private network and do not want to use it from the internet.> > I think you are looking into it too far, its basic really, sometimes I > find rebooting the router (depends on type) will open the ports after > a config change within the router, find its system settings in router, > and use the reboot option if you can find it, else a cold boot – > switch it off for 30sec. > > Regards > > From: Damien Sykes-Lindley > Sent: Friday, July 22, 2016 9:54 PM > To: Icecast streaming server user discussions > Subject: Re: [Icecast] Config and other areas of struggle > > Hi Alan, > In actual fact, I’m having to test everything (server, streamer and > player) on the same machine, which is configured in my router to be > the server. I have opened the port specified in my config and the port > after it and I have set it to allow both TCP and UDP, as I didn’t > know which it used. > I have also tried setting the hostname to my external IP address > rather than a domain, and have even tried linking the port to a bound > address, nothing. In fact if I specify a bind-address it actually > comes up with an error when starting the server itself. > Cheers. > Damien. > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast
Hi Marvin, On 23/07/16 10:03, Marvin Scholz wrote:>> > The hostname should be set to the external hostname of the server, NOT > the internal IP (like 192.168.x.x) unless you only use Icecast in your > private network and do not want to use it from the internet.I must disagree. I have a site [ one of several running icecast2] where we have 2 icecast servers one primary and one backup. They are on the same IP network We have 2 external IP's both running fibre. This allows us to feed audio from server A or server B via IP 1 or IP 2 because either network can and has 'gone down' and sometimes one or other server has failed. [usually power; either UPS or mains] We have outages; we don't have disruption. The hostname has to be ' the buck stops here' and the ip address of the host is preferable because M$ name resolution is not 100% perfect and it's one less thing to go wrong. The external IP address of your modem/router is a waypoint. I have also found that regardless of any instructions this is what you have to do to get it to work. In this instance the network runs both Windows and Linux machines to enable end users to us the software they prefer, while Linux does the heavy lifting. Each router is set to point external clients on port 8000 or 8004 to one or other of the servers on port 8000. One of our external clients is a streaming server, four others are repeaters of the programme. We have a main and a fall back option at each client location. I have 5 possibly 6 Icecast servers all configured the same. The IP address of the host is used in the <hostname></hostname> setting. regards Robert Jeffares -- *Communication Consultants* 64 Warner Park Avenue Laingholm Auckland 0604 09 8176358 0221693124 06 650 6087 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.xiph.org/pipermail/icecast/attachments/20160723/fbd957e9/attachment.html>