<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Hi. Just a (sort of) final question(s).</p>
<p>I have 3 mountpoints running ok in my test virtual machine
Icecast server via port 8000. <br>
</p>
<p> <a class="moz-txt-link-freetext" href="http://10.1.1.41:8000/stream8000">http://10.1.1.41:8000/stream8000</a></p>
<p> <a class="moz-txt-link-freetext" href="http://10.1.1.41:8000/stream8001">http://10.1.1.41:8000/stream8001</a></p>
<p> <a class="moz-txt-link-freetext" href="http://10.1.1.41:8000/stream8002">http://10.1.1.41:8000/stream8002</a></p>
<p>My question is, what is the point of having potential additional
<listen_socket> entries in the icecast.xml? Will port 8000
choke at some point if there are too many mountpoints thus
requiring additional sockets?</p>
<p>Thanks,</p>
<p>Chris.</p>
<p><br>
</p>
<p><br>
</p>
<div class="moz-cite-prefix">On 17/6/21 8:52 am, kit wrote:<br>
</div>
<blockquote type="cite"
cite="mid:f685d892-428d-826e-2f3e-6d9bcb60fc54@iinet.net.au">Hi
Philipp,
<br>
<br>
So I can use several password secured mountpoints all on the
single port 8000. Sounds easy.
<br>
<br>
Thanks,
<br>
<br>
Chris.
<br>
<br>
<br>
On 16/6/21 7:03 pm, Philipp Schafft wrote:
<br>
<blockquote type="cite">Good afternoon,
<br>
<br>
On Wed, 2021-06-16 at 09:27 +0800, kit wrote:
<br>
<blockquote type="cite">Hi Jordan,
<br>
<br>
So does it matter if all authenticated mountpoints use the
same port
<br>
eg 8000?
<br>
<br>
</blockquote>
there is no need to build a second road when you got a second
car. ;)
<br>
<br>
Mountpoints are fully independent. If you need to ensure your
friends
<br>
do can not log into your mount point, then give them another
password.
<br>
That is what Jordan suggested. Using the default username of
"source"
<br>
is a good idea if you don't know the client, that is true.
<br>
Authentication happens per-mount. So also no problem to have the
same
<br>
username for different mounts. (But using a username per user is
surely
<br>
nicer, e.g. when manually reading logs. :)
<br>
<br>
With best regards,
<br>
<br>
<br>
<blockquote type="cite">On 16/6/21 8:45 am, Jordan Erickson
wrote:
<br>
<blockquote type="cite">Hey Chris,
<br>
<br>
That's not really how Icecast mountpoints work. You'd be
much
<br>
better
<br>
off doing source level authentication per-mountpoint. Using
<br>
different
<br>
ports doesn't help your situation unless you're doing some
fancy
<br>
firewalling but if you have a username/password pair entered
<br>
per-mountpoint in the config you can separate any number of
<br>
mountpoints securely. Just note that some source clients
(not sure
<br>
about Mixxx, I use Cool Mic) only allow a 'source' username
for
<br>
connecting to Icecast. I believe you can still specify a
password
<br>
per-mountpoint without username.
<br>
<br>
<br>
Cheers,
<br>
Jordan Erickson
<br>
<br>
<br>
On 6/15/21 5:19 PM, kit wrote:
<br>
<blockquote type="cite">Hi Geoff,
<br>
<br>
My use case is that I have put an icecast server in the
cloud. I
<br>
want
<br>
to stream my stuff on one port and let my friend stream
their
<br>
stuff
<br>
on a different port. I would worry that if they
accidentally
<br>
entered
<br>
the same port as mine in the source client (eg Mixxx) - eg
<br>
<a class="moz-txt-link-freetext" href="http://serverip:8000/mystream8000">http://serverip:8000/mystream8000</a> and
<br>
<a class="moz-txt-link-freetext" href="http://serverip:8000/friendsstream8001">http://serverip:8000/friendsstream8001</a>- it would screw up
both
<br>
our
<br>
streams.
<br>
<br>
Basically I'm looking at this like a safety mechanism,
<br>
particularly
<br>
if I want to add a 3rd stream for another friend.
<br>
<br>
Regards,
<br>
<br>
Chris.
<br>
<br>
On 14/6/21 6:00 pm, Geoff Shang wrote:
<br>
<blockquote type="cite">On Mon, 14 Jun 2021, kit wrote:
<br>
<br>
<blockquote type="cite">Is it possible to assign
specific ports to mountpoints in
<br>
such a
<br>
way that stream8001 can't use port 8000 but only work
on port
<br>
8001?
<br>
</blockquote>
I don't think so.
<br>
<br>
YOu can set up mount aliases that are port-specific but
I don't
<br>
know
<br>
of a way of preventing access to other mounts.
<br>
<br>
So for example, you could put your streams on stream1
and
<br>
stream2
<br>
and set up an alias called stream8000 which specifies
port
<br>
8000 to point to stream1, and an alias stream8001 which
is
<br>
specific
<br>
to port 8001 which points to stream2.
<br>
<br>
Then you could publicise the aliases and hide the
original
<br>
mounts so
<br>
in theory no-one should find them. But I don't think
that
<br>
you'd be
<br>
able to prevent access to stream1 or stream2 on either
port if
<br>
someone actually did find them.
<br>
<br>
I'm curious to know what your use case is.
<br>
<br>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<br>
_______________________________________________
<br>
Icecast mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:Icecast@xiph.org">Icecast@xiph.org</a>
<br>
<a class="moz-txt-link-freetext" href="http://lists.xiph.org/mailman/listinfo/icecast">http://lists.xiph.org/mailman/listinfo/icecast</a>
<br>
</blockquote>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
Icecast mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Icecast@xiph.org">Icecast@xiph.org</a>
<a class="moz-txt-link-freetext" href="http://lists.xiph.org/mailman/listinfo/icecast">http://lists.xiph.org/mailman/listinfo/icecast</a>
</pre>
</blockquote>
</body>
</html>