Kurt, I have retested the Icecast server on port 8000 and it works fine,
but there remains the problem with the IP information from listeners.
Last time I forgot to change data on the client Ices and for that reason
did not work.
Yes, here also the default port is 8000.
I send you two screenshots.
El lun, 05-11-2012 a las 17:12 -0700, Kurt escribi?:
> Send me a snap shot of your router GUI... I dont need any personal
> data, I just want to see
> what it allows you to do....I.E. port forwards....ect
> Routers are not set to any port in particular. The traffic that comes
> in assuming you have no ports
> blocked by your ISP, should allow you to direct ports...
>
> Under residential carriers, Port 25 traffic-out is blocked, Clear.com,
> blocks basically all lower band ports
> I use Logmein to connect to my work station, this operates under a
> concept called Repeater.. There
> by, your carrier thinks its a request from you (modem) so its passed
> through
>
> Also down load CPorts. I tells me what ports are open on the machine
> and who is lock on the port
> ops your not on windows, but I am sure there's something out there
> which will tell you what ports are
> being used... FireWall issues are something you want to look at it
> I also use Nmap (from outside) to scan all ports. That way I am aware
> what ports my modem and
> or ISP are block. They will not be honest with you, so its best to get
> the data yourself
>
> To the best of my knowledge (windows Icecast) is defaulted to 8000.
> Not sure about Linux.
> I have run those boxes, but have not in about a year so I am kinda
> forgetful.
>
> What I dont know off hand is if 8500 is an html port. I.E. pushing a
> standard HTML through port
> 21 will back fire, it is a reserved port...
> Ports I have used for HTML are
>
> 80
> 81
> 8080
> 8000
> 90
> 8081
>
>
> Unless your router is not the first in line, your router should
> respond to any port request....Its up to your system to respond...I.E.
> Software
>
>
>
> On 11/5/2012 2:56 PM, Jos? Luis Artuch wrote:
>
>
> > Kurt, thank you very much again.
> >
> > Listeners hear with the label HTML5. I use only open source software
> > and the system is very basic: Icecast audio server mounted on Debian
> > GNU/Linux on a Pentium IV machine with dynamic IP.
> >
> > I understand how the IP information from listeners is lost when move
> > from port 8000 to port 8500.
> > I am also self-taught, but with my current knowledge I do not get to
> > solve this problem, unless I change the modem/router by another one
> > that does not use the port 8000. This would be an effective
> > solution, but I try to solve the problem in a less drastic way.
> >
> > Is there any way that the Icecast server also listens on port
> > 8000 ?.
> > I've tried to open port 8000 for the Icecast server, but Icecast
on
> > this port has not worked and I've also lost the HTTP connection to
> > the modem/router and I've had to use Telnet to return everything
> > back ... uuffff
> >
> > El lun, 05-11-2012 a las 07:23 -0700, Kurt escribi?:
> >
> > > In a nut shell..
> > >
> > > When a user goes to your port 8000, there is CONTENT in the
> > > Header... This content includes a lot of data, I.E. IP, OS
> > > Browser, ect
> > >
> > > When you translate off of 8000 to 8500, you are dropping the
> > > content and are replacing it with Content from 8500, thus since
> > > 8500 is local, you will not get the outside information
> > > Question is, you should have IceCast listen to 8000.. Otherwise
> > > your content headers will be wrong
> > >
> > > Is there a reason you do this, While I am not a nuclear brain...
> > > Self taught over 30 years, I know what works.. It has to be a
> > > straight shot from outside to IceCast. Otherwise the data is lost
> > > In theory.. If folks are going to your IceCast Directory, and
> > > launching the M3u, you should have this information passed to the
> > > logs, as the User is using a player on his end
> > >
> > > How are your users hearing the music
> > > is it Flash, Html5 or the uses player
> > >
> > > I use Port forwarding
> > >
> > > So............ I have 6 servers at first location, depending on
> > > what has to be served to the public, determines the port
> > > Example
> > > AmericanMusiciansRadio.com by its self responds to port 80. Port
> > > 80 is forwarded to the WebServer
> > > Port 8081 is to another box
> > > Port 90 is another box
> > > Port 21 is another
> > > Port 443 to another
> > > ect ect
> > >
> > > I use virtual hosting. Thus I have one Static IP and use the HTML
> > > headers to steer to the domain. Included in the headers are the
> > > domains that are being requested
> > > This is done through Apache
> > >
> > > These boxes are all separate INTRANET, I use Vmware to get
several
> > > Guest OS's in a box, boxes are Racks There are so many used
> > > commercial boxes out there, (CHEAP) I stopped buying towers a
long
> > > time ago
> > > When you listen to AMR.Alaska, and are hitting me from
> > > AmericanMusiciansRadio.com, Flash is getting its feed from the
> > > IceCast server at another location
> > > the feed is originating at AMRStream.com:8000 which is sitting at
> > > data center with 1 gig up and down. At that location are 7
> > > servers, most of which are running players to feed IceCast.
> > > There is a license (free from Vmware) for up to 4 separate
> > > Sockets, 16 cores.....
> > >
> > >
> > >
> > > Hope that helps
> > >
> > > if you want to call, thats kewl, anything I can do....would love
> > > to help
> > >
> > >
> > >
> > >
> > > Kurt
> > > LSDcode.com
> > > 801.599.1227
> > >
> > >
> > >
> > >
> > >
> > >
> > > On 11/5/2012 6:57 AM, Jos? Luis Artuch wrote:
> > >
> > >
> > > > Kurt, thank you very much for the reply.
> > > > Now I am listening AMR.Alaska :)
> > > >
> > > > The address xxx.xxx.xxx.xxx: 8000 is to access the
modem/router and
> > > > configure it. I tried to change it but I can not find the
way.
> > > >
> > > > With Icecast server running on port 8500, listeners data
(ID, browser,
> > > > OS, etc.) are correct, except your IP:
> > > > http://www.fmcristal3arroyos.com.ar/z/irudi.php
> > > >
> > > > I do not understand what is the problem.
> > > >
> > > > El lun, 05-11-2012 a las 06:24 -0700, Kurt escribi?:
> > > >
> > > > > Okay, Am on desk top so I can address better
> > > > > Example, AmericanMusicansRadio.com is a web site that
uses port 80 to
> > > > > respond to... Standard HTML port.
> > > > > When Flash is loaded to play, it loads
AmrStream.com:8000. Thus ice
> > > > > cast thinks the port of origin is
AmericanMusiciansRadio.com and all I
> > > > > see in the statistics is the IP of the webserver.
> > > > > So the trick is, you want IceCast to listen to Port
8000, thus the
> > > > > content from the HTML (ie. browser, ip OS ect) has the
data and it
> > > > > becomes part of the stats
> > > > > Otherwise, IceCast will do what I have shown in my
example
> > > > > So. Have IceCast listen on the port they are coming
into
> > > > >
> > > > > Kurt
> > > > > LSDcode.com
> > > > > 801.599.1227
> > > > >
> > > > >
> > > > >
> > > >
> > > > I am confused.... if folks are coming in at 8000,
> > > > and is cast is listening on 8500, then the point of origin
is 8500 not
> > > > 8000, thus ice cast is thinking its all local
> > > > Amrstream.com:8000
> > > >
> > > > >
> > > > > On 11/5/2012 5:49 AM, Jos? Luis Artuch wrote:
> > > > >
> > > > >
> > > > > > Hello !!
> > > > > >
> > > > > > I have a modem/router which is accessed through
port 8000 like
> > > > > > xxx.xxx.xxx.xxx:8000, then I put the Icecast
server on port 8500.
> > > > > > Everything works fine except one thing in the
statistics of the
> > > > > > listeners: all listeners are listed with the same
IP, the Icecast
> > > > > > server's IP, not the IP that really have each
one of them.
> > > > > >
> > > > > > Can I change something in the Icecast server to
correct this
> > > > > > problem ?.
> > > > > >
> > > > > > Thanks in advance.
> > > > > > zenbaki
> > > > > >
> > > > > > _______________________________________________
> > > > > > Icecast mailing list
> > > > > > Icecast at xiph.org
> > > > > > http://lists.xiph.org/mailman/listinfo/icecast
> > >
> > >
> >
> >
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.xiph.org/pipermail/icecast/attachments/20121106/78e051b9/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 1.png
Type: image/png
Size: 13863 bytes
Desc: not available
URL:
<http://lists.xiph.org/pipermail/icecast/attachments/20121106/78e051b9/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 2.png
Type: image/png
Size: 23581 bytes
Desc: not available
URL:
<http://lists.xiph.org/pipermail/icecast/attachments/20121106/78e051b9/attachment-0001.png>
