[Spce-user] SPCE 2.8, Kamailio LB only listening on lo

Daniel Grotti dgrotti at sipwise.com
Wed Nov 19 02:59:35 EST 2014


Hi George,
Forgot the shared_ip. Sorry I was thinking to the PRO.
Can you share what the kamailio-lb log says? 
He's showing any errors when you try to stary it?

Daniel
On 18 Nov 2014 19:53, George Mason <george.mason at xoomtalk.com> wrote:
>
> Hi 
>
> I have just installed a new 2.8 instance but am unable to get the 
> Kamailio LB to listen on eth0. The interface is configured correctly and 
> I have checked network.yml, it looks like this: 
>
> hosts: 
>   self: 
>     eth0: 
>       ip: 203.x.x.x 
>       netmask: 255.255.255.248 
>       type: 
>         - web_ext 
>         - sip_ext 
>         - rtp_ext 
>         - ssh_ext 
>     interfaces: 
>       - lo 
>       - eth0 
>     lo: 
>       ip: 127.0.0.1 
>       netmask: 255.255.255.0 
>       shared_ip: [] 
>       shared_v6ip: [] 
>       type: 
>         - sip_int 
>         - ha_int 
>         - web_int 
>       v6ip: '::1' 
>     role: 
>       - proxy 
>       - lb 
>       - mgmt 
>
> Netstat shows that the only listener on UDP 5060 is on lo: 
>
> Active Internet connections (only servers) 
> Proto Recv-Q Send-Q Local Address           Foreign Address        
> State     
> tcp        0      0 0.0.0.0:22              0.0.0.0:*              
> LISTEN    
> tcp        0      0 0.0.0.0:1080            0.0.0.0:*              
> LISTEN    
> tcp        0      0 127.0.0.1:25            0.0.0.0:*              
> LISTEN    
> tcp        0      0 127.0.0.1:8090          0.0.0.0:*              
> LISTEN    
> tcp        0      0 127.0.0.1:5060          0.0.0.0:*              
> LISTEN    
> tcp        0      0 127.0.0.1:5061          0.0.0.0:*              
> LISTEN    
> tcp6       0      0 :::2443                 :::*                   
> LISTEN    
> tcp6       0      0 :::80                   :::*                   
> LISTEN    
> tcp6       0      0 :::22                   :::*                   
> LISTEN    
> tcp6       0      0 ::1:25                  :::*                   
> LISTEN    
> tcp6       0      0 :::443                  :::*                   
> LISTEN    
> tcp6       0      0 :::1443                 :::*                   
> LISTEN    
> tcp6       0      0 ::1:5060                :::*                   
> LISTEN    
> tcp6       0      0 ::1:5061                :::*                   
> LISTEN    
> udp        0      0 127.0.0.1:5040         
> 0.0.0.0:*                         
> udp        0      0 127.0.0.1:5060         
> 0.0.0.0:*                         
> udp        0      0 127.0.0.1:5070         
> 0.0.0.0:*                         
> udp        0      0 127.0.0.1:5080         
> 0.0.0.0:*                         
> udp        0      0 127.0.0.1:4569         
> 0.0.0.0:*                         
> udp        0      0 127.0.0.1:123          
> 0.0.0.0:*                         
> udp6       0      0 127.0.0.1:2222         
> :::*                              
> udp6       0      0 127.0.0.1:2223         
> :::*                              
> udp6       0      0 ::1:5060               
> :::*                              
> udp6       0      0 ::1:123                
> :::*                              
> raw        0      0 0.0.0.0:255             0.0.0.0:*          
>
> What am I missing? Am sure its obvious but can't see it. Could incorrect 
> iptables rules cause this? 
>
> Thanks 
>
> George 
>
>
> _______________________________________________ 
> Spce-user mailing list 
> Spce-user at lists.sipwise.com 
> https://lists.sipwise.com/listinfo/spce-user 


More information about the Spce-user mailing list