i've finally managed to stream in my network with icecast and muse. in the iceast.xml config file i had to specify 192.168.2.5 as my bind-address, my ip in my internal network (i'm behind a router) and from other computers in this network i could hear my streaming. but i would like to stream even out of my network. so i redirected port 8000 of the router to my internal ip, tried to give to a player http://ipoftherouter:8000/live but this time it wouldn't work. so i tried, in the icecast.xml file, to specify as bind-address the ip of the router, but icecast@delirium icecast $ icecast -c icecast.xml Could not create listener socket on port 8000 Server startup failed. Exiting icecast@delirium icecast $ and no other program is using this port: root@delirium root # netstat -anp |grep :8000 root@delirium root # what am i missing? -- Dubitare Disobbedire Disertare ---- Renato Budinich renna.bh@katamail.com
renna wrote:> i've finally managed to stream in my network with icecast and muse. in the > iceast.xml config file i had to specify 192.168.2.5 as my bind-address, my ip > in my internal network (i'm behind a router) and from other computers in this > network i could hear my streaming. but i would like to stream even out of my > network. so i redirected port 8000 of the router to my internal ip, tried to > give to a player http://ipoftherouter:8000/live but this time it wouldn't > work. so i tried, in the icecast.xml file, to specify as bind-address the ip > of the router, but > > icecast@delirium icecast $ icecast -c icecast.xml > Could not create listener socket on port 8000 > Server startup failed. Exiting > icecast@delirium icecast $you can only bind to addresses of interfaces that are in the machine itself.> and no other program is using this port: > > root@delirium root # netstat -anp |grep :8000 > root@delirium root # > > what am i missing?iirc, you have to set the <hostname> to the name of the router to make it work. at least this fixed it for me a while ago. that way, your internal clients should also use your external name, though. regards, j?rn
Hi, I'd personally only use the bind atribute if you realy need to stop it from binding to a specific interface, otherwise you could well come unstuck (e.g. can only hear internally but not externally or vice versa). Not specifying a bind atribute should cause it to bind to all interfaces. And the hostname thing only matters if you use Icecast's generated playlists (i.e. http://server:port/mountpoint.m3u) otherwise it doesn't make any difference (IIRC). As a start with your diagnosis, I suggest looking at your logs for when you tried to connect from outside. If you don't see anything at all, then your client connection wasn't reaching Icecast at all. Geoff. -- Geoff Shang <geoff@hitsandpieces.net> Phone: +61-418-96-5590 MSN: geoff@acbradio.org Make sure your E-mail can be read by everyone! http://www.betips.net/etc/evilmail.html Please avoid sending me Word or PowerPoint attachments. See http://www.fsf.org/philosophy/no-word-attachments.html
first of all i realized i haven't properly understood what <bind-adress> is needed for. to "stick" the server to a particular network card? what does this exactly mean? do i need it? i tried assigning to <hostname> both the internal ip of the router 192.168.2.1 and the ip that's assigned to it by the ISP, and in either case i'm not able through xmms to connect to the stream, neither to http://192.168.2.1:8000/live nor to http://ipassignedbytheISP:8000/live on the router i have redirected port 8000 to my ip both for tcp and for udp, should i change this? btw i created a user icecast to start the icecast server and when i start it it gives me this error, but still starts up, icecast@delirium icecast $ icecast -c icecast/icecast.xml WARNING: Can't change user id unless you are root. does this have anything to do with my problem? thanks for the support so far -- Dubitare Disobbedire Disertare ---- Renato Budinich renna.bh@katamail.com