Icecast Streaming Media Server Forum Index Icecast Streaming Media Server
Icecast is a Xiph Foundation Project
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

Listen on 127.0.0.1/localhost for streamtranscoder

 
Post new topic   Reply to topic    Icecast Streaming Media Server Forum Index -> Icecast Server
View previous topic :: View next topic  
Author Message
rec91402



Joined: 14 Nov 2009
Posts: 32

PostPosted: Thu Aug 12, 2010 8:02 pm    Post subject: Listen on 127.0.0.1/localhost for streamtranscoder Reply with quote

I am trying to use streamtranscoder on my icecast servers.

One I set this up painlessly and working fine...

On my main server, not so pain free.. Crying or Very sad

For what ever reason the main server won't allow streamtranscoder to connect on localhost or 127.0.0.1, but via public IP is fine..

I don't have any listener or bind addresses in the config for the main server.

The server provider INSISTS that 127.0.0.1/localhost is NOT blocked via any firewall settings on port 8000. I beg to differ.... but...until I can prove its not icecasts config they will not resolve it..

I've tried adding a listener and bind to try to force it, but it still doesn't allow a connection 127.0.0.1/localhost

So the only way to get my stream transcoded is to use the public IP, which obviously counts against the bandwidth used per month, which at 24/7/365 is not what I want.

I did NOTHING to my test server setup, and it listens on 127.0.0.1/localhost just fine.

Hints at what I need to look at to make sure that icecast is listening to 127.0.0.1/localhost port 8000 as well?

I've tried all of what I felt was obvious in the config with no joy....

Comments, hints, suggestsions, bigger hammer, kick harder? ? ?

Thanks!
Back to top
View user's profile Send private message
karlH
Code Warrior
Code Warrior


Joined: 13 Jun 2005
Posts: 5476
Location: UK

PostPosted: Thu Aug 12, 2010 8:37 pm    Post subject: Reply with quote

look at the netstat output for the local address of sockets in a listen state (eg netstat -tnl). If you are on a bind socket then you'll see the IP in the entry instead of 0.0.0.0.

Besides the listening aspect of icecast, there is also the routing and firewalls. Does ping and a simple connection to 127.0.0.1:8000 work (eg curl/wget)?

karl.
Back to top
View user's profile Send private message Send e-mail Visit poster's website
rec91402



Joined: 14 Nov 2009
Posts: 32

PostPosted: Fri Aug 13, 2010 1:48 pm    Post subject: Reply with quote

karlH wrote:
look at the netstat output for the local address of sockets in a listen state (eg netstat -tnl). If you are on a bind socket then you'll see the IP in the entry instead of 0.0.0.0.

Besides the listening aspect of icecast, there is also the routing and firewalls. Does ping and a simple connection to 127.0.0.1:8000 work (eg curl/wget)?

karl.


netstat result

Code:

root@rcc [~]# netstat -tnl
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address               Foreign Address             State
tcp        0      0 0.0.0.0:2087                0.0.0.0:*                   LISTEN
tcp        0      0 0.0.0.0:3306                0.0.0.0:*                   LISTEN
tcp        0      0 127.0.0.1:783               0.0.0.0:*                   LISTEN
tcp        0      0 0.0.0.0:2095                0.0.0.0:*                   LISTEN
tcp        0      0 0.0.0.0:111                 0.0.0.0:*                   LISTEN
tcp        0      0 0.0.0.0:2096                0.0.0.0:*                   LISTEN
tcp        0      0 0.0.0.0:80                  0.0.0.0:*                   LISTEN
tcp        0      0 0.0.0.0:465                 0.0.0.0:*                   LISTEN
tcp        0      0 174.xxx.xxx.xxx:53           0.0.0.0:*                   LISTEN
tcp        0      0 174.xxx.xxx.xxx:53           0.0.0.0:*                   LISTEN
tcp        0      0 127.0.0.1:53                0.0.0.0:*                   LISTEN
tcp        0      0 0.0.0.0:21                  0.0.0.0:*                   LISTEN
tcp        0      0 0.0.0.0:25                  0.0.0.0:*                   LISTEN
tcp        0      0 127.0.0.1:953               0.0.0.0:*                   LISTEN
tcp        0      0 0.0.0.0:443                 0.0.0.0:*                   LISTEN
tcp        0      0 0.0.0.0:2077                0.0.0.0:*                   LISTEN
tcp        0      0 0.0.0.0:2078                0.0.0.0:*                   LISTEN
tcp        0      0 174.xxx.xxx.xxx:8000         0.0.0.0:*                   LISTEN
tcp        0      0 174.xxx.xxx.xxx:8001         0.0.0.0:*                   LISTEN
tcp        0      0 0.0.0.0:1                   0.0.0.0:*                   LISTEN
tcp        0      0 0.0.0.0:2082                0.0.0.0:*                   LISTEN
tcp        0      0 0.0.0.0:2083                0.0.0.0:*                   LISTEN
tcp        0      0 0.0.0.0:2086                0.0.0.0:*                   LISTEN
tcp        0      0 :::110                      :::*                        LISTEN
tcp        0      0 :::143                      :::*                        LISTEN
tcp        0      0 :::465                      :::*                        LISTEN
tcp        0      0 :::21                       :::*                        LISTEN
tcp        0      0 :::22                       :::*                        LISTEN
tcp        0      0 :::25                       :::*                        LISTEN
tcp        0      0 :::993                      :::*                        LISTEN
tcp        0      0 :::995                      :::*                        LISTEN


Ping does work to 127.0.0.1/localhost

Host provider is ADIMANT that firewall is not the issue, but icecast, quite honestly I call BS... suffice it say I've called them everything under the sun due to some very boneheaded setup on some things... that took 15 HOURS to install streamtranscoder on because they intentially disable repos that are standard for any other host... Evil or Very Mad Twisted Evil

I've done a fireawall stop and no joy... so while as much as I'd like it to be a host issue... it appears that icecast is not listening on the localhost..

I've tried putting things like:

Code:

    <listen-socket>
        <port>8000</port>
    <bind-address>127.0.0.1</bind-address>
    </listen-socket>



No joy....

this is the netstat from my testing server that works

Code:

root@host [~]# netstat -tnl
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address               Foreign Address             State
tcp        0      0 0.0.0.0:1                   0.0.0.0:*                   LISTEN
tcp        0      0 0.0.0.0:993                 0.0.0.0:*                   LISTEN
tcp        0      0 0.0.0.0:51234               0.0.0.0:*                   LISTEN
tcp        0      0 0.0.0.0:2082                0.0.0.0:*                   LISTEN
tcp        0      0 0.0.0.0:2083                0.0.0.0:*                   LISTEN
tcp        0      0 0.0.0.0:995                 0.0.0.0:*                   LISTEN
tcp        0      0 0.0.0.0:2086                0.0.0.0:*                   LISTEN
tcp        0      0 0.0.0.0:2087                0.0.0.0:*                   LISTEN
tcp        0      0 127.0.0.1:199               0.0.0.0:*                   LISTEN
tcp        0      0 0.0.0.0:3306                0.0.0.0:*                   LISTEN
tcp        0      0 0.0.0.0:110                 0.0.0.0:*                   LISTEN
tcp        0      0 127.0.0.1:783               0.0.0.0:*                   LISTEN
tcp        0      0 0.0.0.0:2095                0.0.0.0:*                   LISTEN
tcp        0      0 0.0.0.0:111                 0.0.0.0:*                   LISTEN
tcp        0      0 0.0.0.0:143                 0.0.0.0:*                   LISTEN
tcp        0      0 0.0.0.0:80                  0.0.0.0:*                   LISTEN
tcp        0      0 0.0.0.0:2096                0.0.0.0:*                   LISTEN
tcp        0      0 0.0.0.0:465                 0.0.0.0:*                   LISTEN
tcp        0      0 208.xxx.xx.xxx:53           0.0.0.0:*                   LISTEN
tcp        0      0 208.xxx.xxx.xxx:53           0.0.0.0:*                   LISTEN
tcp        0      0 208.xx.xxx.xxx:53           0.0.0.0:*                   LISTEN
tcp        0      0 208.xxx.xxx.xxxx:53           0.0.0.0:*                   LISTEN
tcp        0      0 208.xxx.xxx.xxxx:53            0.0.0.0:*                   LISTEN
tcp        0      0 xxxx.xxx0.xxx:53               0.0.0.0:*                   LISTEN
tcp        0      0 127.0.0.1:53                0.0.0.0:*                   LISTEN
tcp        0      0 0.0.0.0:21                  0.0.0.0:*                   LISTEN
tcp        0      0 0.0.0.0:25                  0.0.0.0:*                   LISTEN
tcp        0      0 127.0.0.1:953               0.0.0.0:*                   LISTEN
tcp        0      0 0.0.0.0:443                 0.0.0.0:*                   LISTEN
tcp        0      0 0.0.0.0:2077                0.0.0.0:*                   LISTEN
tcp        0      0 0.0.0.0:2078                0.0.0.0:*                   LISTEN
tcp        0      0 :::8000                     :::*                        LISTEN
tcp        0      0 :::465                      :::*                        LISTEN
tcp        0      0 :::21                       :::*                        LISTEN
tcp        0      0 :::22                       :::*                        LISTEN
tcp        0      0 :::25                       :::*                        LISTEN
root@host [~]#
Back to top
View user's profile Send private message
karlH
Code Warrior
Code Warrior


Joined: 13 Jun 2005
Posts: 5476
Location: UK

PostPosted: Fri Aug 13, 2010 3:41 pm    Post subject: Reply with quote

tcp 0 0 174.xxx.xxx.xxx:8000 0.0.0.0:* LISTEN

so it looks like a bind is being given, it also looks like you have a shoutcast compatible port as well, which makes me wonder whether you have 2 listen-sockets defined or a shoutcast-mount in the listen-socket for port 8000. If you have neither then I would suspect that an icecast is being run using a different xml to what you are thinking of. Check the ps aux | grep icecast output to see the actual path of the xml and see if you are using anything like chroot jail as that could indicate a different location for the xml. You can always try change the port number to see if the netstat shows the difference.

karl.
Back to top
View user's profile Send private message Send e-mail Visit poster's website
iunderwood



Joined: 23 Aug 2008
Posts: 114
Location: Leicester, MA

PostPosted: Sun Aug 15, 2010 9:09 pm    Post subject: Reply with quote

Looking at the netstat output, there are no sockets for your Icecast except on the public iP. If this were open to everything, you'd see a 0.0.0.0:8000/8001 in the Local Address column for IPv4 only sockets.

If you're being billed entirely by traffic that goes out the network interface, then I don't think you'll be billed, because the traffic to and from the same host never leaves the machine. You'll need to find a way to verify that.
_________________
++I;
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic   Reply to topic    Icecast Streaming Media Server Forum Index -> Icecast Server All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © 2001, 2002 phpBB Group
subRebel style by ktauber