Icecast Streaming Media Server

mkido · Posted: Tue Oct 26, 2010 7:04 pm Post subject: Excuse me, I forgot about it.

Yeah, just right now, I reminded about it (netstat -tnlp) , and I confirmed it by your comment, thanks, thanks. I already learned about it, but hadn't assimilated.

Here it is, the server is listening 8000 port by "icecast". Both local address and foreign address are 0 0.0.0.0:8000, 0.0.0.0:*, respectively. What is those quadrets of "0.0.0.0" signify?

I have been switching around in icecast.xml configuration file's hostname to,
(1) localhost
(2) 127.0.0.1
(3) 64.214.83.249
just like trails and errors,

Right now, it is (3) 64.214.83.249. Do you think it is better to put back (2) 127.0.0.1, as you suggested me a few times, depending on my Network situation. Should I better ask the colocation administrator, Azteca.Net Inc, an Internet service provuder (ISP)? I am still vague about this topic, when it is better set to which one, so excuse me.

Unlikely, but regarding firewall, I made it "Enabled", and Trusted Services go through firewall are FTP, Mail(SMTP), NFS4, SSH, Samba, SecureWWW(HTTPS) right now.

mkido

[root@biwa ~]# netstat -tnlp
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:8000 0.0.0.0:* LISTEN 4548/icecast
tcp 0 0 127.0.0.1:2208 0.0.0.0:* LISTEN 2032/hpiod
tcp 0 0 0.0.0.0:3306 0.0.0.0:* LISTEN 2167/mysqld
tcp 0 0 0.0.0.0:750 0.0.0.0:* LISTEN 1840/rpc.statd
tcp 0 0 192.168.122.1:53 0.0.0.0:* LISTEN 2504/dnsmasq
tcp 0 0 0.0.0.0:21 0.0.0.0:* LISTEN 2076/vsftpd
tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN 2049/cupsd
tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN 2211/sendmail: acce
tcp 0 0 127.0.0.1:2207 0.0.0.0:* LISTEN 2037/python
tcp 0 0 :::111 :::* LISTEN 1811/rpcbind
tcp 0 0 :::80 :::* LISTEN 7921/httpd
tcp 0 0 :::22 :::* LISTEN 2063/sshd
tcp 0 0 :::443 :::* LISTEN 7921/httpd
[root@biwa ~]#

mkido · Posted: Tue Oct 26, 2010 7:08 pm Post subject: I missed code tag.

karlH · Code Warrior Joined: 13 Jun 2005 Posts: 5476 Location: UK

The hostname should be set to the name/IP your listeners would use, if that is the 64... IP then ok, if its a DNS name then fine. 127.0.0.1 is not a good one to use as it is of no use to people on the internet. The reason it works for many is that it is only used for a few small cases, like directory listing. This setting is not the cause of the lack of connectivity.

As I said before, if icecast is listening on port 8000 (which your netstat does indicate) then the problem is the forwarding of the external requests by your router.

Try to think this through. If I was to connect to your icecast to get the status page, then I would put your eternal address port 8000 into a browser. The request then makes its way through your ISP to your router and then our router needs to forward it onto the internal machine.

A couple of areas that may be tripping you up,

Make sure you are not firewalling TCP port 8000 on either the icecast box or the router.

go to whatsmyip.org to verify the external address is as expected, you can use that site o check for an open port as well (8000)

karl.

mkido

Hi! Karl, thanks, thanks many times.

Before I am going to ask ISP's help about packet transmissions and a router setting, I still want to check around the company's server itself. This time, as my first experience, I looked at the server's firewall status (iptables).

I don't see icecast in the list (neither ACCEPT, nor REJEST) in iptables. Should I put icecast as ACCEPT as a trust service through the firewall? If you think better, I would do, but I have to study how to do it.

karlH · Code Warrior Joined: 13 Jun 2005 Posts: 5476 Location: UK

yes you will need to add port 8000 as a trusted port.

karl.

mkido

OK, thanks, I will study adding it as a trusted service by a command line. A little while later.

mkido

mkido

Wow, wonderful and great karl,

I GOT IT WORKING! It was due to firewall "iptables". I have been reading carefully FedoraProject documentation about how to edit the "iptables" by command line. The editing step is fairly complicated command line, so I dare not yet to try it. Meanwhile, before editing firewall, it must be stopped, then after editing it must be restarted. I learned about it, these two steps are so-so easy,

karlH · Code Warrior Joined: 13 Jun 2005 Posts: 5476 Location: UK

you should find a gui tool for editing the firewall, just look for trusted services. there is a system-config-firewall-tui if you are over a text only link. Just click forward past the common list of ports and add port 8000 on the other ports list. That will maintain the port access over reboots.

karl.

mkido · Posted: Tue Nov 02, 2010 12:04 am Post subject: thank you again.

Dear karl, thanks many times.

Actually I have done it by a command line and, editor nano. It worked. I did it according to the blog which was posted in "kernel-panic.org" and the date of the post was Wed, 18 Apr 2007. and questinee was Néstor, and answeree was Michael J McCafferty. The title of post is "Re: How to check port 8000". It is a very concise blog, but it just worked in my case also. In short, I edited "/etc/sysconfig/iptables" manually. It isn't a recommended way by RedHat, but just only one line addition about 8000 ACCEPT, so it appears OK.

I also examined about GUI tool "system-config-firewall-tui" -> customize, which you mentioned. Sound great! I will use it next time. Thank you again.

mkido