Hello I tried searching the mailing list and did some googling on the topic also, but didn't find anything very useful. I'm looking for a way to restrict access to my icecast2 server (which runs on a Slackware 8.1 system) by using a list of IPs that should be allowed to connect as clients / sources. .. now how do I do this? ;-) I remember that it was possible in the older Icecast version to have rules in the configuration file, but since the docs on Icecast2 aren't complete, I have no clue on how to do this. So, once again, I'll be glad to accept your help :-) Thanks! --- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage: http://www.icecast.org/ To unsubscribe from this list, send a message to 'icecast-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.
On Tuesday 25 February 2003 03:55, Jesper Johnson wrote:> Hello > > I tried searching the mailing list and did some googling on the topic also, > but didn't find anything very useful. I'm looking for a way to restrict > access to my icecast2 server (which runs on a Slackware 8.1 system) > by using a list of IPs that should be allowed to connect as clients / > sources. .. now how do I do this? ;-) I remember that it was possible in > the older Icecast version to have rules in the configuration file, but > since the docs on Icecast2 aren't complete, I have no clue on how to do > this. >Not currently supported. Patches are welcome. Mike --- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage: http://www.icecast.org/ To unsubscribe from this list, send a message to 'icecast-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.
It just occurred to me that setting up a simple IPtables script might be just as easy. Aside from the default firewall that comes with the latest Red Hat Linux, you could try the GUI tool fwbuilder (fwbuilder.org). Just installed it on a test RH 8.0 system with great success. Simply create the hosts and services and networks you want, then click and drag to create the rule sets. Your config is saved in XML format. Then click compile and you have viable script. You can set up the range of IP addresses you want to access the box while keeping port 8000 open only for them. It's a pretty nifty little tool for users not wanting to dirty their hands with raw IPtables scripts. Hope that helps. KJ <p>On Tue, 2003-02-25 at 15:51, Steve Meuse wrote:> Jesper Johnson expunged (jesper.johnson@welho.com): > > > I tried searching the mailing list and did some googling on the topic also, > > but didn't find anything very useful. I'm looking for a way to restrict > > access to my icecast2 server (which runs on a Slackware 8.1 system) > > by using a list of IPs that should be allowed to connect as clients / sources. > > .. now how do I do this? ;-) I remember that it was possible in the older > > Icecast version to have rules in the configuration file, but since the > > docs on Icecast2 aren't complete, I have no clue on how to do this. > > I always recommend using a filtering router, but that tends not to be an > option for most people. Kernel packet filtering is probably what I would > recommend. I like to keep these types of functions out of user land, but > ymmv. > > -Steve > > > -- > Progress (n.): The process through which the Internet has evolved from smart > people in front of dumb terminals to dumb people in front of smart terminals. > -- > --- >8 ---- > List archives: http://www.xiph.org/archives/ > icecast project homepage: http://www.icecast.org/ > To unsubscribe from this list, send a message to 'icecast-request@xiph.org' > containing only the word 'unsubscribe' in the body. No subject is needed. > Unsubscribe messages sent to the list will be ignored/filtered.-- /-----------------------------\__/--------------------------------\ | Kerry J. Cox __ kerry.cox@ksl.com | | KSL System Administrator | | p: 801.575.7771 | | http://www.ksl.com/ |__| f: 801.575.5745 | | GPG Key: __ http://quasi.ksl.com/kerry.asc | \-----------------------------/ \--------------------------------/ <p> -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 233 bytes Desc: This is a digitally signed message part Url : http://lists.xiph.org/pipermail/icecast/attachments/20030225/43c14ef9/signature.pgp
Hello. I want to know how I can put files (mp3s or oggs) on my webserver, make a plsylist and stream them directly from the webserver. I had found an apps witch could do that on the old website, but not on the new one.. I also want to know what app you advise me for stream mp3s to a icecast server (in ogg) under linux. Because I've seen DSP for winamp, but no apps for streaming from a linux mp3/ogg player. Sorry for my poor english Regards Ruben <p><p><p>--- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage: http://www.icecast.org/ To unsubscribe from this list, send a message to 'icecast-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.
I would think the /etc/hosts.allow and /etc/hosts.deny would do the trick. /etc/hosts.allow icecast: 127.0.0.1 64.147.130. 192.168.0. /etc/hosts.deny ALL: ALL Someone please correct me if I am wrong. It's been known to happen. KJ On Mon, 2003-02-24 at 09:55, Jesper Johnson wrote:> Hello > > I tried searching the mailing list and did some googling on the topic also, > but didn't find anything very useful. I'm looking for a way to restrict > access to my icecast2 server (which runs on a Slackware 8.1 system) > by using a list of IPs that should be allowed to connect as clients / sources. > .. now how do I do this? ;-) I remember that it was possible in the older > Icecast version to have rules in the configuration file, but since the > docs on Icecast2 aren't complete, I have no clue on how to do this. > > So, once again, I'll be glad to accept your help :-) > Thanks! > --- >8 ---- > List archives: http://www.xiph.org/archives/ > icecast project homepage: http://www.icecast.org/ > To unsubscribe from this list, send a message to 'icecast-request@xiph.org' > containing only the word 'unsubscribe' in the body. No subject is needed. > Unsubscribe messages sent to the list will be ignored/filtered.-- /-----------------------------\__/--------------------------------\ | Kerry J. Cox __ kerry.cox@ksl.com | | KSL System Administrator | | p: 801.575.7771 | | http://www.ksl.com/ |__| f: 801.575.5745 | | GPG Key: __ http://quasi.ksl.com/kerry.asc | \-----------------------------/ \--------------------------------/ <p> -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 233 bytes Desc: This is a digitally signed message part Url : http://lists.xiph.org/pipermail/icecast/attachments/20030224/affd3beb/signature.pgp
Hello how do i log into the admin console of icecast2? i tried telnet as i used to do with icecast 1. but the server closes the connection immediately. pls. help. thanks, deva --- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage: http://www.icecast.org/ To unsubscribe from this list, send a message to 'icecast-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.
Hi there. On Mon, Feb 24, 2003 at 09:59:46AM -0700, Kerry Cox wrote:> I would think the /etc/hosts.allow and /etc/hosts.deny would do the > trick. > /etc/hosts.allow > icecast: 127.0.0.1 64.147.130. 192.168.0. > /etc/hosts.deny > ALL: ALL > Someone please correct me if I am wrong. It's been known to happen. > KJAs i have not seen any --with-libwrap in icecast configure script,i don't think /etc/hosts.allow and /etc/hosts.deny will be used (i may be wrong however :) ). I guess a way to restrict all connection by ip would be to use some firewall rules. A more flexible way would be to use the <mount> node in icecast.xml and put a password and a login for mountpoint to restrict acces at. I havent play with this yet, but i guess if it s in the config file it may work. This would not be an ip based restriction but would still let the administrator tell who can and cannot connect to icecast. Hope this helps. Pierre Amadio <p><p><p>--- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage: http://www.icecast.org/ To unsubscribe from this list, send a message to 'icecast-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.
Jesper Johnson expunged (jesper.johnson@welho.com):> I tried searching the mailing list and did some googling on the topic also, > but didn't find anything very useful. I'm looking for a way to restrict > access to my icecast2 server (which runs on a Slackware 8.1 system) > by using a list of IPs that should be allowed to connect as clients / sources. > .. now how do I do this? ;-) I remember that it was possible in the older > Icecast version to have rules in the configuration file, but since the > docs on Icecast2 aren't complete, I have no clue on how to do this.I always recommend using a filtering router, but that tends not to be an option for most people. Kernel packet filtering is probably what I would recommend. I like to keep these types of functions out of user land, but ymmv. -Steve <p> -- Progress (n.): The process through which the Internet has evolved from smart people in front of dumb terminals to dumb people in front of smart terminals. -- --- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage: http://www.icecast.org/ To unsubscribe from this list, send a message to 'icecast-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.