<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.30.3">
</HEAD>
<BODY TEXT="#000000" BGCOLOR="#ffffff">
<FONT COLOR="#000080">Ok Kurt, thank you !!</FONT><BR>
<BR>
El mar, 06-11-2012 a las 10:38 -0700, Kurt escribió:
<BLOCKQUOTE TYPE=CITE>
Sorry for the slow response. Today, I am swamped, hope to be able to help you tomorrow<BR>
<BR>
Kurt<BR>
LSDcode.com<BR>
801.599.1227<BR>
<BR>
<BR>
On 11/5/2012 8:45 PM, José Luis Artuch wrote:<BR>
<BR>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
<BLOCKQUOTE TYPE=CITE>
<FONT COLOR="#000080">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.</FONT><BR>
<FONT COLOR="#000080">Last time I forgot to change data on the client Ices and for that reason did not work.</FONT><BR>
<BR>
<FONT COLOR="#000080">Yes, here also the default port is 8000.</FONT><BR>
<BR>
<FONT COLOR="#000080">I send you two screenshots.</FONT><BR>
<BR>
El lun, 05-11-2012 a las 17:12 -0700, Kurt escribió: <BR>
<BLOCKQUOTE TYPE=CITE>
Send me a snap shot of your router GUI... I dont need any personal data, I just want to see<BR>
what it allows you to do....I.E. port forwards....ect<BR>
Routers are not set to any port in particular. The traffic that comes in assuming you have no ports<BR>
blocked by your ISP, should allow you to direct ports...<BR>
<BR>
Under residential carriers, Port 25 traffic-out is blocked, Clear.com, blocks basically all lower band ports<BR>
I use Logmein to connect to my work station, this operates under a concept called Repeater.. There<BR>
by, your carrier thinks its a request from you (modem) so its passed through<BR>
<BR>
Also down load CPorts. I tells me what ports are open on the machine and who is lock on the port<BR>
ops your not on windows, but I am sure there's something out there which will tell you what ports are<BR>
being used... FireWall issues are something you want to look at it<BR>
I also use Nmap (from outside) to scan all ports. That way I am aware what ports my modem and<BR>
or ISP are block. They will not be honest with you, so its best to get the data yourself<BR>
<BR>
To the best of my knowledge (windows Icecast) is defaulted to 8000. Not sure about Linux.<BR>
I have run those boxes, but have not in about a year so I am kinda forgetful.<BR>
<BR>
What I dont know off hand is if 8500 is an html port. I.E. pushing a standard HTML through port<BR>
21 will back fire, it is a reserved port...<BR>
Ports I have used for HTML are<BR>
<BR>
80<BR>
81<BR>
8080<BR>
8000<BR>
90<BR>
8081<BR>
<BR>
<BR>
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<BR>
<BR>
<BR>
<BR>
On 11/5/2012 2:56 PM, José Luis Artuch wrote:<BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
<FONT COLOR="#000080">Kurt, thank you very much again.</FONT><BR>
<BR>
<FONT COLOR="#000080">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.</FONT><BR>
<BR>
<FONT COLOR="#000080">I understand how the IP information from listeners is lost when move from port 8000 to port 8500.</FONT><BR>
<FONT COLOR="#000080">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.</FONT><BR>
<BR>
<FONT COLOR="#000080">Is there any way that the Icecast server also listens on port 8000 ?.</FONT><BR>
<FONT COLOR="#000080">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</FONT><BR>
<BR>
El lun, 05-11-2012 a las 07:23 -0700, Kurt escribió: <BR>
<BLOCKQUOTE TYPE=CITE>
In a nut shell..<BR>
<BR>
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<BR>
<BR>
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<BR>
Question is, you should have IceCast listen to 8000.. Otherwise your content headers will be wrong<BR>
<BR>
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<BR>
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<BR>
<BR>
How are your users hearing the music<BR>
is it Flash, Html5 or the uses player<BR>
<BR>
I use Port forwarding<BR>
<BR>
So............ I have 6 servers at first location, depending on what has to be served to the public, determines the port<BR>
Example<BR>
AmericanMusiciansRadio.com by its self responds to port 80. Port 80 is forwarded to the WebServer<BR>
Port 8081 is to another box<BR>
Port 90 is another box<BR>
Port 21 is another<BR>
Port 443 to another<BR>
ect ect<BR>
<BR>
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<BR>
This is done through Apache<BR>
<BR>
These boxes are all separate <FONT COLOR="#ff0000">INTRA</FONT>NET, 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<BR>
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<BR>
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.<BR>
There is a license (free from Vmware) for up to 4 separate Sockets, 16 cores..... <BR>
<BR>
<BR>
<BR>
Hope that helps<BR>
<BR>
if you want to call, thats kewl, anything I can do....would love to help<BR>
<BR>
<BR>
<BR>
<BR>
Kurt<BR>
LSDcode.com<BR>
801.599.1227<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
On 11/5/2012 6:57 AM, José Luis Artuch wrote:<BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
<PRE>
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:
<A HREF="http://www.fmcristal3arroyos.com.ar/z/irudi.php">http://www.fmcristal3arroyos.com.ar/z/irudi.php</A>
I do not understand what is the problem.
El lun, 05-11-2012 a las 06:24 -0700, Kurt escribió:
</PRE>
<BLOCKQUOTE TYPE=CITE>
<PRE>
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
</PRE>
</BLOCKQUOTE>
<PRE>
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
</PRE>
<BLOCKQUOTE TYPE=CITE>
<PRE>
On 11/5/2012 5:49 AM, José Luis Artuch wrote:
</PRE>
<BLOCKQUOTE TYPE=CITE>
<PRE>
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
<A HREF="mailto:Icecast@xiph.org">Icecast@xiph.org</A>
<A HREF="http://lists.xiph.org/mailman/listinfo/icecast">http://lists.xiph.org/mailman/listinfo/icecast</A>
</PRE>
</BLOCKQUOTE>
</BLOCKQUOTE>
</BLOCKQUOTE>
<BR>
</BLOCKQUOTE>
<BR>
</BLOCKQUOTE>
<BR>
</BLOCKQUOTE>
<BR>
<BR>
<BR>
</BLOCKQUOTE>
<BR>
</BLOCKQUOTE>
<BR>
</BODY>
</HTML>