[Users] Re: [openser] fail to listen on two addresses

Bogdan-Andrei Iancu bogdan at voice-system.ro
Tue Aug 22 15:05:13 CEST 2006


Hi,

that's right - have you checked the syslog? if openser is in no fork 
mode and multiple interfaces are configured, an warning about this is 
generated at startup.

regards,
bogdan

Jeremie Le Hen wrote:

>Hi,
>
>I didn't use to reply to my self, by I eventually understood what was
>going wrong and I wish to post it for the record.
>
>Actually, using the -D flag -- which prevents OpenSER from forking --,
>prevents from listening on more than one IP address.
>
>I think this ought to be noted in the manpage.
>
>Sorry for the noise.
>Regards,
>
>-- Jeremie
>
>On Mon, Jul 31, 2006 at 07:41:35PM +0200, Jeremie Le Hen wrote:
>  
>
>>Hi list,
>>
>>I am new two OpenSER.  I installed OpenSER 1.1.0-notls and I need it
>>to listen on both 127.0.0.1 and one of my physical interface's IP address.
>>
>>The manual page states:
>>%      -l address  Listens  on  the  specified  address/interface. Multiple -l
>>%                  mean listening on multiple addresses. The address format is
>>%                  [proto:]address[:port], where proto = udp|tcp and address =
>>%                  host|ip_address|interface_name. Example: -l  localhost,  -l
>>%                  udp:127.0.0.1:5080, -l eth0:5062.  The default behaviour is
>>%                  to listen on all the ipv4 interfaces.
>>
>>I tried the following command-line, without success.  I cannot connect to
>>either one of the IP address I specified, depending on the order I provided
>>them :
>>
>>% openser -u voipproxy -g voipproxy  -l 84.xxx.xxx.xxx -l 127.0.0.1 -D -E
>>
>>And in another terminal:
>>
>>% # lsof -nPi4 -ap `pgrep -d, openser`
>>% COMMAND   PID      USER   FD   TYPE DEVICE SIZE NODE NAME
>>% openser 30837 voipproxy    5u  IPv4  60272       UDP 84.xxx.xxx.xxx:5060 
>>% openser 30838 voipproxy    5u  IPv4  60272       UDP 84.xxx.xxx.xxx:5060 
>>% openser 30839 voipproxy    5u  IPv4  60272       UDP 84.xxx.xxx.xxx:5060 
>>
>>
>>If I turn the command-line to:
>>
>>% openser -u voipproxy -g voipproxy -l 127.0.0.1 -l 84.xxx.xxx.xxx -D -E
>>
>>I get:
>>
>>% # lsof -nPi4 -ap `pgrep -d, openser`
>>% COMMAND   PID      USER   FD   TYPE DEVICE SIZE NODE NAME
>>% openser 30845 voipproxy    5u  IPv4  60382       UDP 127.0.0.1:5060 
>>% openser 30846 voipproxy    5u  IPv4  60382       UDP 127.0.0.1:5060 
>>% openser 30847 voipproxy    5u  IPv4  60382       UDP 127.0.0.1:5060 
>>
>>
>>Note that in both case I get:
>>% Listening on 
>>%              udp: 84.xxx.xxx.xxx [84.xxx.xxx.xxx]:5060
>>%              udp: 127.0.0.1 [127.0.0.1]:5060
>>%              tcp: 84.xxx.xxx.xxx [84.xxx.xxx.xxx]:5060
>>%              tcp: 127.0.0.1 [127.0.0.1]:5060
>>
>>Except the order change, following the command-line.
>>
>>
>>I could have missed something and would be glad if someone pointed it
>>out to me.
>>
>>Thank you.
>>Regards,
>>    
>>
>
>  
>





More information about the Users mailing list