From therealkitman at iinet.net.au Mon Jun 14 02:07:55 2021 From: therealkitman at iinet.net.au (kit) Date: Mon, 14 Jun 2021 10:07:55 +0800 Subject: [Icecast] Multiple mountpoints and ports Message-ID: <56d82b36-3965-6467-d254-a71a613f31fe@iinet.net.au> Hi, I have two mountpoints (stream8000 and stream8001) and two ports (8000 and 8001) in use. But I have found that either mountpoints can use both ports. EG. http://serverip:8000/stream8001 and http://serverip:8001/stream8001 both work. Is it possible to assign specific ports to mountpoints in such a way that stream8001 can't use port 8000 but only work on port 8001? I have gone through the icecast.xml and docs but couldn't find an answer. Thanks, Chris. From lr at pripple.de Mon Jun 14 08:34:18 2021 From: lr at pripple.de (Lorenz Reichelt) Date: Mon, 14 Jun 2021 10:34:18 +0200 Subject: [Icecast] Multiple mountpoints and ports In-Reply-To: <56d82b36-3965-6467-d254-a71a613f31fe@iinet.net.au> References: <56d82b36-3965-6467-d254-a71a613f31fe@iinet.net.au> Message-ID: <4B2D36C7-D12B-4AF2-9608-17DA22235CA2@pripple.de> Hi Chris, interesting question! Have you tried adding the listen-socket definitions inside the mount point definition? This would seem like the natural way and it wouldn?t take long to try it out ? It?s not documented, so it might just not work, then you could turn that into a feature request. Best regards, Lorenz -------------- next part -------------- An HTML attachment was scrubbed... URL: From geoff at QuiteLikely.com Mon Jun 14 10:00:42 2021 From: geoff at QuiteLikely.com (Geoff Shang) Date: Mon, 14 Jun 2021 13:00:42 +0300 (IDT) Subject: [Icecast] Multiple mountpoints and ports In-Reply-To: <56d82b36-3965-6467-d254-a71a613f31fe@iinet.net.au> References: <56d82b36-3965-6467-d254-a71a613f31fe@iinet.net.au> Message-ID: On Mon, 14 Jun 2021, kit wrote: > Is it possible to assign specific ports to mountpoints in such a way that > stream8001 can't use port 8000 but only work on port 8001? I don't think so. YOu can set up mount aliases that are port-specific but I don't know of a way of preventing access to other mounts. So for example, you could put your streams on stream1 and stream2 and set up an alias called stream8000 which specifies port 8000 to point to stream1, and an alias stream8001 which is specific to port 8001 which points to stream2. Then you could publicise the aliases and hide the original mounts so in theory no-one should find them. But I don't think that you'd be able to prevent access to stream1 or stream2 on either port if someone actually did find them. I'm curious to know what your use case is. Cheers, Geoff. From therealkitman at iinet.net.au Wed Jun 16 00:18:39 2021 From: therealkitman at iinet.net.au (kit) Date: Wed, 16 Jun 2021 08:18:39 +0800 Subject: [Icecast] Multiple mountpoints and ports In-Reply-To: <4B2D36C7-D12B-4AF2-9608-17DA22235CA2@pripple.de> References: <56d82b36-3965-6467-d254-a71a613f31fe@iinet.net.au> <4B2D36C7-D12B-4AF2-9608-17DA22235CA2@pripple.de> Message-ID: Hi Lorenz,? that may be worth a shot. I'll test that shortly. Thanks. On 14/6/21 4:34 pm, Lorenz Reichelt wrote: > Hi Chris, interesting question! Have you tried adding the listen-socket definitions inside the mount point definition? This would seem like the natural way and it wouldn?t take long to try it out ? It?s not documented, so it might just not work, then you could turn that into a feature request. Best regards, Lorenz > > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast -------------- next part -------------- An HTML attachment was scrubbed... URL: From therealkitman at iinet.net.au Wed Jun 16 00:19:10 2021 From: therealkitman at iinet.net.au (kit) Date: Wed, 16 Jun 2021 08:19:10 +0800 Subject: [Icecast] Multiple mountpoints and ports In-Reply-To: References: <56d82b36-3965-6467-d254-a71a613f31fe@iinet.net.au> Message-ID: Hi Geoff, My use case is that I have put an icecast server in the cloud. I want to stream my stuff on one port and let my friend stream their stuff on a different port. I would worry that if they accidentally entered the same port as mine in the source client (eg Mixxx) - eg http://serverip:8000/mystream8000 and http://serverip:8000/friendsstream8001- it would screw up both our streams. Basically I'm looking at this like a safety mechanism, particularly if I want to add a 3rd stream for another friend. Regards, Chris. On 14/6/21 6:00 pm, Geoff Shang wrote: > On Mon, 14 Jun 2021, kit wrote: > >> Is it possible to assign specific ports to mountpoints in such a way >> that stream8001 can't use port 8000 but only work on port 8001? > > I don't think so. > > YOu can set up mount aliases that are port-specific but I don't know > of a way of preventing access to other mounts. > > So for example, you could put your streams on stream1 and stream2 and > set up an alias called stream8000 which specifies port > 8000 to point to stream1, and an alias stream8001 which is specific to > port 8001 which points to stream2. > > Then you could publicise the aliases and hide the original mounts so > in theory no-one should find them.? But I don't think that you'd be > able to prevent access to stream1 or stream2 on either port if someone > actually did find them. > > I'm curious to know what your use case is. > > Cheers, > Geoff. > > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast From jordan at coolmic.net Wed Jun 16 00:45:04 2021 From: jordan at coolmic.net (Jordan Erickson) Date: Tue, 15 Jun 2021 17:45:04 -0700 Subject: [Icecast] Multiple mountpoints and ports In-Reply-To: References: <56d82b36-3965-6467-d254-a71a613f31fe@iinet.net.au> Message-ID: Hey Chris, That's not really how Icecast mountpoints work. You'd be much better off doing source level authentication per-mountpoint. Using different ports doesn't help your situation unless you're doing some fancy firewalling but if you have a username/password pair entered per-mountpoint in the config you can separate any number of mountpoints securely. Just note that some source clients (not sure about Mixxx, I use Cool Mic) only allow a 'source' username for connecting to Icecast. I believe you can still specify a password per-mountpoint without username. Cheers, Jordan Erickson On 6/15/21 5:19 PM, kit wrote: > Hi Geoff, > > My use case is that I have put an icecast server in the cloud. I want to > stream my stuff on one port and let my friend stream their stuff on a > different port. I would worry that if they accidentally entered the same > port as mine in the source client (eg Mixxx) - eg > http://serverip:8000/mystream8000 and > http://serverip:8000/friendsstream8001- it would screw up both our streams. > > Basically I'm looking at this like a safety mechanism, particularly if I > want to add a 3rd stream for another friend. > > Regards, > > Chris. > > On 14/6/21 6:00 pm, Geoff Shang wrote: >> On Mon, 14 Jun 2021, kit wrote: >> >>> Is it possible to assign specific ports to mountpoints in such a way >>> that stream8001 can't use port 8000 but only work on port 8001? >> >> I don't think so. >> >> YOu can set up mount aliases that are port-specific but I don't know >> of a way of preventing access to other mounts. >> >> So for example, you could put your streams on stream1 and stream2 and >> set up an alias called stream8000 which specifies port >> 8000 to point to stream1, and an alias stream8001 which is specific to >> port 8001 which points to stream2. >> >> Then you could publicise the aliases and hide the original mounts so >> in theory no-one should find them.? But I don't think that you'd be >> able to prevent access to stream1 or stream2 on either port if someone >> actually did find them. >> >> I'm curious to know what your use case is. >> >> Cheers, >> Geoff. >> >> _______________________________________________ >> Icecast mailing list >> Icecast at xiph.org >> http://lists.xiph.org/mailman/listinfo/icecast > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast From therealkitman at iinet.net.au Wed Jun 16 01:27:36 2021 From: therealkitman at iinet.net.au (kit) Date: Wed, 16 Jun 2021 09:27:36 +0800 Subject: [Icecast] Multiple mountpoints and ports In-Reply-To: References: <56d82b36-3965-6467-d254-a71a613f31fe@iinet.net.au> Message-ID: <1a95d820-8cd3-e0ba-ee41-e34420e7dc7a@iinet.net.au> Hi Jordan, So does it matter if all authenticated mountpoints use the same port eg 8000? BTW - Mixxx allows multiple usernames. Thanks, Chris. On 16/6/21 8:45 am, Jordan Erickson wrote: > Hey Chris, > > That's not really how Icecast mountpoints work. You'd be much better > off doing source level authentication per-mountpoint. Using different > ports doesn't help your situation unless you're doing some fancy > firewalling but if you have a username/password pair entered > per-mountpoint in the config you can separate any number of > mountpoints securely. Just note that some source clients (not sure > about Mixxx, I use Cool Mic) only allow a 'source' username for > connecting to Icecast. I believe you can still specify a password > per-mountpoint without username. > > > Cheers, > Jordan Erickson > > > On 6/15/21 5:19 PM, kit wrote: >> Hi Geoff, >> >> My use case is that I have put an icecast server in the cloud. I want >> to stream my stuff on one port and let my friend stream their stuff >> on a different port. I would worry that if they accidentally entered >> the same port as mine in the source client (eg Mixxx) - eg >> http://serverip:8000/mystream8000 and >> http://serverip:8000/friendsstream8001- it would screw up both our >> streams. >> >> Basically I'm looking at this like a safety mechanism, particularly >> if I want to add a 3rd stream for another friend. >> >> Regards, >> >> Chris. >> >> On 14/6/21 6:00 pm, Geoff Shang wrote: >>> On Mon, 14 Jun 2021, kit wrote: >>> >>>> Is it possible to assign specific ports to mountpoints in such a >>>> way that stream8001 can't use port 8000 but only work on port 8001? >>> >>> I don't think so. >>> >>> YOu can set up mount aliases that are port-specific but I don't know >>> of a way of preventing access to other mounts. >>> >>> So for example, you could put your streams on stream1 and stream2 >>> and set up an alias called stream8000 which specifies port >>> 8000 to point to stream1, and an alias stream8001 which is specific >>> to port 8001 which points to stream2. >>> >>> Then you could publicise the aliases and hide the original mounts so >>> in theory no-one should find them.? But I don't think that you'd be >>> able to prevent access to stream1 or stream2 on either port if >>> someone actually did find them. >>> >>> I'm curious to know what your use case is. >>> >>> Cheers, >>> Geoff. >>> >>> _______________________________________________ >>> Icecast mailing list >>> Icecast at xiph.org >>> http://lists.xiph.org/mailman/listinfo/icecast >> _______________________________________________ >> Icecast mailing list >> Icecast at xiph.org >> http://lists.xiph.org/mailman/listinfo/icecast From cf at it-flash.de Wed Jun 16 07:18:30 2021 From: cf at it-flash.de (Christian "flash2" Fladung) Date: Wed, 16 Jun 2021 09:18:30 +0200 Subject: [Icecast] Multiple mountpoints and ports In-Reply-To: References: <56d82b36-3965-6467-d254-a71a613f31fe@iinet.net.au> Message-ID: <444ade2a-c546-4663-b499-c0bb10a0d7cc@it-flash.de> Ports should be only give a? service. ?BlueMail for Android herunterladen ? Am 16. Juni 2021 2:19 AM, um 2:19 AM, kit schrieb: >Hi Geoff, > >My use case is that I have put an icecast server in the cloud. I want >to >stream my stuff on one port and let my friend stream their stuff on a >different port. I would worry that if they accidentally entered the >same >port as mine in the source client (eg Mixxx) - eg >http://serverip:8000/mystream8000 and >http://serverip:8000/friendsstream8001- it would screw up both our >streams. > >Basically I'm looking at this like a safety mechanism, particularly if >I >want to add a 3rd stream for another friend. > >Regards, > >Chris. > >On 14/6/21 6:00 pm, Geoff Shang wrote: >> On Mon, 14 Jun 2021, kit wrote: >> >>> Is it possible to assign specific ports to mountpoints in such a way > >>> that stream8001 can't use port 8000 but only work on port 8001? >> >> I don't think so. >> >> YOu can set up mount aliases that are port-specific but I don't know >> of a way of preventing access to other mounts. >> >> So for example, you could put your streams on stream1 and stream2 and > >> set up an alias called stream8000 which specifies port >> 8000 to point to stream1, and an alias stream8001 which is specific >to >> port 8001 which points to stream2. >> >> Then you could publicise the aliases and hide the original mounts so >> in theory no-one should find them.? But I don't think that you'd be >> able to prevent access to stream1 or stream2 on either port if >someone >> actually did find them. >> >> I'm curious to know what your use case is. >> >> Cheers, >> Geoff. >> >> _______________________________________________ >> Icecast mailing list >> Icecast at xiph.org >> http://lists.xiph.org/mailman/listinfo/icecast >_______________________________________________ >Icecast mailing list >Icecast at xiph.org >http://lists.xiph.org/mailman/listinfo/icecast -------------- next part -------------- An HTML attachment was scrubbed... URL: From therealkitman at iinet.net.au Wed Jun 16 10:12:51 2021 From: therealkitman at iinet.net.au (kit) Date: Wed, 16 Jun 2021 18:12:51 +0800 Subject: [Icecast] Multiple mountpoints and ports In-Reply-To: <444ade2a-c546-4663-b499-c0bb10a0d7cc@it-flash.de> References: <56d82b36-3965-6467-d254-a71a613f31fe@iinet.net.au> <444ade2a-c546-4663-b499-c0bb10a0d7cc@it-flash.de> Message-ID: <627d9dc1-605c-54cc-5755-3ea371406093@iinet.net.au> Sorry, I'm not too sure what you mean. On 16/6/21 3:18 pm, Christian "flash2" Fladung wrote: > Ports should be only give a? service. > > ?BlueMail for Android herunterladen ? > > Am 16. Juni 2021 2:19 AM, um 2:19 AM, kit schrieb: >> Hi Geoff, >> >> My use case is that I have put an icecast server in the cloud. I want >> to >> stream my stuff on one port and let my friend stream their stuff on a >> different port. I would worry that if they accidentally entered the >> same >> port as mine in the source client (eg Mixxx) - eg >> http://serverip:8000/mystream8000 and >> http://serverip:8000/friendsstream8001- it would screw up both our >> streams. >> >> Basically I'm looking at this like a safety mechanism, particularly if >> I >> want to add a 3rd stream for another friend. >> >> Regards, >> >> Chris. >> >> On 14/6/21 6:00 pm, Geoff Shang wrote: >>> On Mon, 14 Jun 2021, kit wrote: >>> >>>> Is it possible to assign specific ports to mountpoints in such a way >>>> that stream8001 can't use port 8000 but only work on port 8001? >>> I don't think so. >>> >>> YOu can set up mount aliases that are port-specific but I don't know >>> of a way of preventing access to other mounts. >>> >>> So for example, you could put your streams on stream1 and stream2 and >>> set up an alias called stream8000 which specifies port >>> 8000 to point to stream1, and an alias stream8001 which is specific >> to >>> port 8001 which points to stream2. >>> >>> Then you could publicise the aliases and hide the original mounts so >>> in theory no-one should find them.? But I don't think that you'd be >>> able to prevent access to stream1 or stream2 on either port if >> someone >>> actually did find them. >>> >>> I'm curious to know what your use case is. >>> >>> Cheers, >>> Geoff. >>> >>> _______________________________________________ >>> Icecast mailing list >>> Icecast at xiph.org >>> http://lists.xiph.org/mailman/listinfo/icecast >> _______________________________________________ >> Icecast mailing list >> Icecast at xiph.org >> http://lists.xiph.org/mailman/listinfo/icecast > > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast -------------- next part -------------- An HTML attachment was scrubbed... URL: From phschafft at de.loewenfelsen.net Wed Jun 16 11:03:20 2021 From: phschafft at de.loewenfelsen.net (Philipp Schafft) Date: Wed, 16 Jun 2021 11:03:20 +0000 Subject: [Icecast] Multiple mountpoints and ports In-Reply-To: <1a95d820-8cd3-e0ba-ee41-e34420e7dc7a@iinet.net.au> References: <56d82b36-3965-6467-d254-a71a613f31fe@iinet.net.au> <1a95d820-8cd3-e0ba-ee41-e34420e7dc7a@iinet.net.au> Message-ID: <2311872d70efb8f07cf6f3b735b28083e75b8cc0.camel@de.loewenfelsen.net> Good afternoon, On Wed, 2021-06-16 at 09:27 +0800, kit wrote: > Hi Jordan, > > So does it matter if all authenticated mountpoints use the same port > eg 8000? > there is no need to build a second road when you got a second car. ;) Mountpoints are fully independent. If you need to ensure your friends do can not log into your mount point, then give them another password. That is what Jordan suggested. Using the default username of "source" is a good idea if you don't know the client, that is true. Authentication happens per-mount. So also no problem to have the same username for different mounts. (But using a username per user is surely nicer, e.g. when manually reading logs. :) With best regards, > > On 16/6/21 8:45 am, Jordan Erickson wrote: > > Hey Chris, > > > > That's not really how Icecast mountpoints work. You'd be much > > better > > off doing source level authentication per-mountpoint. Using > > different > > ports doesn't help your situation unless you're doing some fancy > > firewalling but if you have a username/password pair entered > > per-mountpoint in the config you can separate any number of > > mountpoints securely. Just note that some source clients (not sure > > about Mixxx, I use Cool Mic) only allow a 'source' username for > > connecting to Icecast. I believe you can still specify a password > > per-mountpoint without username. > > > > > > Cheers, > > Jordan Erickson > > > > > > On 6/15/21 5:19 PM, kit wrote: > > > Hi Geoff, > > > > > > My use case is that I have put an icecast server in the cloud. I > > > want > > > to stream my stuff on one port and let my friend stream their > > > stuff > > > on a different port. I would worry that if they accidentally > > > entered > > > the same port as mine in the source client (eg Mixxx) - eg > > > http://serverip:8000/mystream8000 and > > > http://serverip:8000/friendsstream8001- it would screw up both > > > our > > > streams. > > > > > > Basically I'm looking at this like a safety mechanism, > > > particularly > > > if I want to add a 3rd stream for another friend. > > > > > > Regards, > > > > > > Chris. > > > > > > On 14/6/21 6:00 pm, Geoff Shang wrote: > > > > On Mon, 14 Jun 2021, kit wrote: > > > > > > > > > Is it possible to assign specific ports to mountpoints in > > > > > such a > > > > > way that stream8001 can't use port 8000 but only work on port > > > > > 8001? > > > > > > > > I don't think so. > > > > > > > > YOu can set up mount aliases that are port-specific but I don't > > > > know > > > > of a way of preventing access to other mounts. > > > > > > > > So for example, you could put your streams on stream1 and > > > > stream2 > > > > and set up an alias called stream8000 which specifies port > > > > 8000 to point to stream1, and an alias stream8001 which is > > > > specific > > > > to port 8001 which points to stream2. > > > > > > > > Then you could publicise the aliases and hide the original > > > > mounts so > > > > in theory no-one should find them. But I don't think that > > > > you'd be > > > > able to prevent access to stream1 or stream2 on either port if > > > > someone actually did find them. > > > > > > > > I'm curious to know what your use case is. > > > > -- Philipp Schafft (CEO/Gesch?ftsf?hrer) Telephon: +49.3535 490 17 92 L?wenfelsen UG (haftungsbeschr?nkt) Registration number: Bickinger Stra?e 21 HRB 12308 CB 04916 Herzberg (Elster) VATIN/USt-ID: Germany DE305133015 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 523 bytes Desc: This is a digitally signed message part URL: From therealkitman at iinet.net.au Thu Jun 17 00:52:41 2021 From: therealkitman at iinet.net.au (kit) Date: Thu, 17 Jun 2021 08:52:41 +0800 Subject: [Icecast] Multiple mountpoints and ports In-Reply-To: <2311872d70efb8f07cf6f3b735b28083e75b8cc0.camel@de.loewenfelsen.net> References: <56d82b36-3965-6467-d254-a71a613f31fe@iinet.net.au> <1a95d820-8cd3-e0ba-ee41-e34420e7dc7a@iinet.net.au> <2311872d70efb8f07cf6f3b735b28083e75b8cc0.camel@de.loewenfelsen.net> Message-ID: Hi Philipp, So I can use several password secured mountpoints all on the single port 8000. Sounds easy. Thanks, Chris. On 16/6/21 7:03 pm, Philipp Schafft wrote: > Good afternoon, > > On Wed, 2021-06-16 at 09:27 +0800, kit wrote: >> Hi Jordan, >> >> So does it matter if all authenticated mountpoints use the same port >> eg 8000? >> > there is no need to build a second road when you got a second car. ;) > > Mountpoints are fully independent. If you need to ensure your friends > do can not log into your mount point, then give them another password. > That is what Jordan suggested. Using the default username of "source" > is a good idea if you don't know the client, that is true. > Authentication happens per-mount. So also no problem to have the same > username for different mounts. (But using a username per user is surely > nicer, e.g. when manually reading logs. :) > > With best regards, > > >> On 16/6/21 8:45 am, Jordan Erickson wrote: >>> Hey Chris, >>> >>> That's not really how Icecast mountpoints work. You'd be much >>> better >>> off doing source level authentication per-mountpoint. Using >>> different >>> ports doesn't help your situation unless you're doing some fancy >>> firewalling but if you have a username/password pair entered >>> per-mountpoint in the config you can separate any number of >>> mountpoints securely. Just note that some source clients (not sure >>> about Mixxx, I use Cool Mic) only allow a 'source' username for >>> connecting to Icecast. I believe you can still specify a password >>> per-mountpoint without username. >>> >>> >>> Cheers, >>> Jordan Erickson >>> >>> >>> On 6/15/21 5:19 PM, kit wrote: >>>> Hi Geoff, >>>> >>>> My use case is that I have put an icecast server in the cloud. I >>>> want >>>> to stream my stuff on one port and let my friend stream their >>>> stuff >>>> on a different port. I would worry that if they accidentally >>>> entered >>>> the same port as mine in the source client (eg Mixxx) - eg >>>> http://serverip:8000/mystream8000 and >>>> http://serverip:8000/friendsstream8001- it would screw up both >>>> our >>>> streams. >>>> >>>> Basically I'm looking at this like a safety mechanism, >>>> particularly >>>> if I want to add a 3rd stream for another friend. >>>> >>>> Regards, >>>> >>>> Chris. >>>> >>>> On 14/6/21 6:00 pm, Geoff Shang wrote: >>>>> On Mon, 14 Jun 2021, kit wrote: >>>>> >>>>>> Is it possible to assign specific ports to mountpoints in >>>>>> such a >>>>>> way that stream8001 can't use port 8000 but only work on port >>>>>> 8001? >>>>> I don't think so. >>>>> >>>>> YOu can set up mount aliases that are port-specific but I don't >>>>> know >>>>> of a way of preventing access to other mounts. >>>>> >>>>> So for example, you could put your streams on stream1 and >>>>> stream2 >>>>> and set up an alias called stream8000 which specifies port >>>>> 8000 to point to stream1, and an alias stream8001 which is >>>>> specific >>>>> to port 8001 which points to stream2. >>>>> >>>>> Then you could publicise the aliases and hide the original >>>>> mounts so >>>>> in theory no-one should find them. But I don't think that >>>>> you'd be >>>>> able to prevent access to stream1 or stream2 on either port if >>>>> someone actually did find them. >>>>> >>>>> I'm curious to know what your use case is. >>>>> > > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast -------------- next part -------------- An HTML attachment was scrubbed... URL: From therealkitman at iinet.net.au Wed Jun 23 06:23:11 2021 From: therealkitman at iinet.net.au (kit) Date: Wed, 23 Jun 2021 14:23:11 +0800 Subject: [Icecast] Multiple mountpoints and ports In-Reply-To: References: <56d82b36-3965-6467-d254-a71a613f31fe@iinet.net.au> <4B2D36C7-D12B-4AF2-9608-17DA22235CA2@pripple.de> Message-ID: <60377264-9738-d89a-a20c-37ece025e3d6@iinet.net.au> Bottom line - listen-sockets defs in mountpoint defs did nothing. On 16/6/21 8:18 am, kit wrote: > Hi Lorenz,? that may be worth a shot. I'll test that shortly. > > Thanks. > > On 14/6/21 4:34 pm, Lorenz Reichelt wrote: >> Hi Chris, interesting question! Have you tried adding the >> listen-socket definitions inside the mount point definition? This >> would seem like the natural way and it wouldn?t take long to try it >> out ? It?s not documented, so it might just not work, then you could >> turn that into a feature request. Best regards, Lorenz >> >> _______________________________________________ >> Icecast mailing list >> Icecast at xiph.org >> http://lists.xiph.org/mailman/listinfo/icecast > > > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast -------------- next part -------------- An HTML attachment was scrubbed... URL: From therealkitman at iinet.net.au Wed Jun 23 06:23:42 2021 From: therealkitman at iinet.net.au (kit) Date: Wed, 23 Jun 2021 14:23:42 +0800 Subject: [Icecast] Multiple mountpoints and ports In-Reply-To: References: <56d82b36-3965-6467-d254-a71a613f31fe@iinet.net.au> <1a95d820-8cd3-e0ba-ee41-e34420e7dc7a@iinet.net.au> <2311872d70efb8f07cf6f3b735b28083e75b8cc0.camel@de.loewenfelsen.net> Message-ID: Hi. Just a (sort of) final question(s). I have 3 mountpoints running ok in my test virtual machine Icecast server via port 8000. ??? http://10.1.1.41:8000/stream8000 ??? http://10.1.1.41:8000/stream8001 ??? http://10.1.1.41:8000/stream8002 My question is, what is the point of having potential additional entries in the icecast.xml? Will port 8000 choke at some point if there are too many mountpoints thus requiring additional sockets? Thanks, Chris. On 17/6/21 8:52 am, kit wrote: > Hi Philipp, > > So I can use several password secured mountpoints all on the single > port 8000. Sounds easy. > > Thanks, > > Chris. > > > On 16/6/21 7:03 pm, Philipp Schafft wrote: >> Good afternoon, >> >> On Wed, 2021-06-16 at 09:27 +0800, kit wrote: >>> Hi Jordan, >>> >>> So does it matter if all authenticated mountpoints use the same port >>> eg 8000? >>> >> there is no need to build a second road when you got a second car. ;) >> >> Mountpoints are fully independent. If you need to ensure your friends >> do can not log into your mount point, then give them another password. >> That is what Jordan suggested. Using the default username of "source" >> is a good idea if you don't know the client, that is true. >> Authentication happens per-mount. So also no problem to have the same >> username for different mounts. (But using a username per user is surely >> nicer, e.g. when manually reading logs. :) >> >> With best regards, >> >> >>> On 16/6/21 8:45 am, Jordan Erickson wrote: >>>> Hey Chris, >>>> >>>> That's not really how Icecast mountpoints work. You'd be much >>>> better >>>> off doing source level authentication per-mountpoint. Using >>>> different >>>> ports doesn't help your situation unless you're doing some fancy >>>> firewalling but if you have a username/password pair entered >>>> per-mountpoint in the config you can separate any number of >>>> mountpoints securely. Just note that some source clients (not sure >>>> about Mixxx, I use Cool Mic) only allow a 'source' username for >>>> connecting to Icecast. I believe you can still specify a password >>>> per-mountpoint without username. >>>> >>>> >>>> Cheers, >>>> Jordan Erickson >>>> >>>> >>>> On 6/15/21 5:19 PM, kit wrote: >>>>> Hi Geoff, >>>>> >>>>> My use case is that I have put an icecast server in the cloud. I >>>>> want >>>>> to stream my stuff on one port and let my friend stream their >>>>> stuff >>>>> on a different port. I would worry that if they accidentally >>>>> entered >>>>> the same port as mine in the source client (eg Mixxx) - eg >>>>> http://serverip:8000/mystream8000 and >>>>> http://serverip:8000/friendsstream8001- it would screw up both >>>>> our >>>>> streams. >>>>> >>>>> Basically I'm looking at this like a safety mechanism, >>>>> particularly >>>>> if I want to add a 3rd stream for another friend. >>>>> >>>>> Regards, >>>>> >>>>> Chris. >>>>> >>>>> On 14/6/21 6:00 pm, Geoff Shang wrote: >>>>>> On Mon, 14 Jun 2021, kit wrote: >>>>>> >>>>>>> Is it possible to assign specific ports to mountpoints in >>>>>>> such a >>>>>>> way that stream8001 can't use port 8000 but only work on port >>>>>>> 8001? >>>>>> I don't think so. >>>>>> >>>>>> YOu can set up mount aliases that are port-specific but I don't >>>>>> know >>>>>> of a way of preventing access to other mounts. >>>>>> >>>>>> So for example, you could put your streams on stream1 and >>>>>> stream2 >>>>>> and set up an alias called stream8000 which specifies port >>>>>> 8000 to point to stream1, and an alias stream8001 which is >>>>>> specific >>>>>> to port 8001 which points to stream2. >>>>>> >>>>>> Then you could publicise the aliases and hide the original >>>>>> mounts so >>>>>> in theory no-one should find them.? But I don't think that >>>>>> you'd be >>>>>> able to prevent access to stream1 or stream2 on either port if >>>>>> someone actually did find them. >>>>>> >>>>>> I'm curious to know what your use case is. >>>>>> >> >> _______________________________________________ >> Icecast mailing list >> Icecast at xiph.org >> http://lists.xiph.org/mailman/listinfo/icecast > > > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast -------------- next part -------------- An HTML attachment was scrubbed... URL: From railgun.michael at gmail.com Wed Jun 23 06:42:52 2021 From: railgun.michael at gmail.com (Railgun) Date: Wed, 23 Jun 2021 08:42:52 +0200 Subject: [Icecast] Multiple mountpoints and ports In-Reply-To: References: <56d82b36-3965-6467-d254-a71a613f31fe@iinet.net.au> <1a95d820-8cd3-e0ba-ee41-e34420e7dc7a@iinet.net.au> <2311872d70efb8f07cf6f3b735b28083e75b8cc0.camel@de.loewenfelsen.net> Message-ID: For example you can enable SSL support on a difrent port. kit schrieb am Mi., 23. Juni 2021, 08:23: > Hi. Just a (sort of) final question(s). > > I have 3 mountpoints running ok in my test virtual machine Icecast server > via port 8000. > > http://10.1.1.41:8000/stream8000 > > http://10.1.1.41:8000/stream8001 > > http://10.1.1.41:8000/stream8002 > > My question is, what is the point of having potential additional > entries in the icecast.xml? Will port 8000 choke at some > point if there are too many mountpoints thus requiring additional sockets? > > Thanks, > > Chris. > > > > On 17/6/21 8:52 am, kit wrote: > > Hi Philipp, > > So I can use several password secured mountpoints all on the single port > 8000. Sounds easy. > > Thanks, > > Chris. > > > On 16/6/21 7:03 pm, Philipp Schafft wrote: > > Good afternoon, > > On Wed, 2021-06-16 at 09:27 +0800, kit wrote: > > Hi Jordan, > > So does it matter if all authenticated mountpoints use the same port > eg 8000? > > there is no need to build a second road when you got a second car. ;) > > Mountpoints are fully independent. If you need to ensure your friends > do can not log into your mount point, then give them another password. > That is what Jordan suggested. Using the default username of "source" > is a good idea if you don't know the client, that is true. > Authentication happens per-mount. So also no problem to have the same > username for different mounts. (But using a username per user is surely > nicer, e.g. when manually reading logs. :) > > With best regards, > > > On 16/6/21 8:45 am, Jordan Erickson wrote: > > Hey Chris, > > That's not really how Icecast mountpoints work. You'd be much > better > off doing source level authentication per-mountpoint. Using > different > ports doesn't help your situation unless you're doing some fancy > firewalling but if you have a username/password pair entered > per-mountpoint in the config you can separate any number of > mountpoints securely. Just note that some source clients (not sure > about Mixxx, I use Cool Mic) only allow a 'source' username for > connecting to Icecast. I believe you can still specify a password > per-mountpoint without username. > > > Cheers, > Jordan Erickson > > > On 6/15/21 5:19 PM, kit wrote: > > Hi Geoff, > > My use case is that I have put an icecast server in the cloud. I > want > to stream my stuff on one port and let my friend stream their > stuff > on a different port. I would worry that if they accidentally > entered > the same port as mine in the source client (eg Mixxx) - eg > http://serverip:8000/mystream8000 and > http://serverip:8000/friendsstream8001- it would screw up both > our > streams. > > Basically I'm looking at this like a safety mechanism, > particularly > if I want to add a 3rd stream for another friend. > > Regards, > > Chris. > > On 14/6/21 6:00 pm, Geoff Shang wrote: > > On Mon, 14 Jun 2021, kit wrote: > > Is it possible to assign specific ports to mountpoints in > such a > way that stream8001 can't use port 8000 but only work on port > 8001? > > I don't think so. > > YOu can set up mount aliases that are port-specific but I don't > know > of a way of preventing access to other mounts. > > So for example, you could put your streams on stream1 and > stream2 > and set up an alias called stream8000 which specifies port > 8000 to point to stream1, and an alias stream8001 which is > specific > to port 8001 which points to stream2. > > Then you could publicise the aliases and hide the original > mounts so > in theory no-one should find them. But I don't think that > you'd be > able to prevent access to stream1 or stream2 on either port if > someone actually did find them. > > I'm curious to know what your use case is. > > > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast > > > > _______________________________________________ > Icecast mailing listIcecast at xiph.orghttp://lists.xiph.org/mailman/listinfo/icecast > > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast > -------------- next part -------------- An HTML attachment was scrubbed... URL: From phschafft at de.loewenfelsen.net Wed Jun 23 09:30:41 2021 From: phschafft at de.loewenfelsen.net (Philipp Schafft) Date: Wed, 23 Jun 2021 09:30:41 +0000 Subject: [Icecast] Multiple mountpoints and ports In-Reply-To: <60377264-9738-d89a-a20c-37ece025e3d6@iinet.net.au> References: <56d82b36-3965-6467-d254-a71a613f31fe@iinet.net.au> <4B2D36C7-D12B-4AF2-9608-17DA22235CA2@pripple.de> <60377264-9738-d89a-a20c-37ece025e3d6@iinet.net.au> Message-ID: Good morning, On Wed, 2021-06-23 at 14:23 +0800, kit wrote: > Bottom line - listen-sockets defs in mountpoint defs did nothing. correct, as both objects types are independent they can not be mixed. With best regards, > On 16/6/21 8:18 am, kit wrote: > > Hi Lorenz, that may be worth a shot. I'll test that shortly. > > > > Thanks. > > > > On 14/6/21 4:34 pm, Lorenz Reichelt wrote: > > > Hi Chris, interesting question! Have you tried adding the > > > listen-socket definitions inside the mount point definition? > > > This > > > would seem like the natural way and it wouldn?t take long to try > > > it > > > out ? It?s not documented, so it might just not work, then you > > > could > > > turn that into a feature request. Best regards, Lorenz > > -- Philipp Schafft (CEO/Gesch?ftsf?hrer) Telephon: +49.3535 490 17 92 L?wenfelsen UG (haftungsbeschr?nkt) Registration number: Bickinger Stra?e 21 HRB 12308 CB 04916 Herzberg (Elster) VATIN/USt-ID: Germany DE305133015 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 523 bytes Desc: This is a digitally signed message part URL: From phschafft at de.loewenfelsen.net Wed Jun 23 09:34:31 2021 From: phschafft at de.loewenfelsen.net (Philipp Schafft) Date: Wed, 23 Jun 2021 09:34:31 +0000 Subject: [Icecast] Multiple mountpoints and ports In-Reply-To: References: <56d82b36-3965-6467-d254-a71a613f31fe@iinet.net.au> <1a95d820-8cd3-e0ba-ee41-e34420e7dc7a@iinet.net.au> <2311872d70efb8f07cf6f3b735b28083e75b8cc0.camel@de.loewenfelsen.net> Message-ID: <67c366cc89df87b5d9e0f44f78a9a1be548023e2.camel@de.loewenfelsen.net> Good morning, On Wed, 2021-06-23 at 08:42 +0200, Railgun wrote: > For example you can enable SSL support on a difrent port. This (I hope you mean TLS ;) is one of the classic examples[0]. Another one is for mixed IPv6 and IPv4 setups or when you have internal and external networks. Still this is all for a bit more advanced (such as TLS) to very advanced setups. :) With best regards, [0] Icecast 2.4.x requires separate ports. Icecast 2.5.x can handle TLS and non-TLS traffic on the same port(s). > kit schrieb am Mi., 23. Juni 2021, > 08:23: > > > Hi. Just a (sort of) final question(s). > > > > I have 3 mountpoints running ok in my test virtual machine Icecast > > server > > via port 8000. > > > > http://10.1.1.41:8000/stream8000 > > > > http://10.1.1.41:8000/stream8001 > > > > http://10.1.1.41:8000/stream8002 > > > > My question is, what is the point of having potential additional > > entries in the icecast.xml? Will port 8000 choke at > > some > > point if there are too many mountpoints thus requiring additional > > sockets? > > > > Thanks, > > > > Chris. > > > > > > > > On 17/6/21 8:52 am, kit wrote: > > > > Hi Philipp, > > > > So I can use several password secured mountpoints all on the single > > port 8000. Sounds easy. > > -- Philipp Schafft (CEO/Gesch?ftsf?hrer) Telephon: +49.3535 490 17 92 L?wenfelsen UG (haftungsbeschr?nkt) Registration number: Bickinger Stra?e 21 HRB 12308 CB 04916 Herzberg (Elster) VATIN/USt-ID: Germany DE305133015 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 523 bytes Desc: This is a digitally signed message part URL: From subscription at nextdial.com.br Thu Jun 24 17:46:31 2021 From: subscription at nextdial.com.br (subscription) Date: Thu, 24 Jun 2021 14:46:31 -0300 Subject: [Icecast] Silent, no user interaction Icecast install (Ubuntu) Message-ID: Hello guys, I am trying to develop a script to configure new machines so I need a way to silently and without user interaction needed install Icecast. I already tryed "sudo apt-get install -qq icecast2" but an automated configuration window is displayed. Is there a way or another option to achieve that? Best, Thiago -------------- next part -------------- An HTML attachment was scrubbed... URL: From petr.pisar at atlas.cz Thu Jun 24 18:14:45 2021 From: petr.pisar at atlas.cz (Petr Pisar) Date: Thu, 24 Jun 2021 20:14:45 +0200 Subject: [Icecast] Silent, no user interaction Icecast install (Ubuntu) In-Reply-To: References: Message-ID: V?Thu, Jun 24, 2021 at 02:46:31PM -0300,?subscription napsal(a): > I am trying to develop a script to configure new machines so I need a way to > silently and without user interaction needed install Icecast. > > I already tryed "sudo apt-get install -qq icecast2" but an automated > configuration window is displayed. > You should rather ask at because the interactive configuration is an add-on of your distributor. -- Petr -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: