[Freeswitch-users] freeswtich request on port 4242?

Terry Barnum terry at digital-outpost.com
Mon Mar 24 19:11:41 MSK 2014


Thank you very much for the thoughtful responses Lawrence, Ken and Steve.

-Terry

On Mar 24, 2014, at 1:35 AM, Steven Ayre <steveayre at gmail.com> wrote:

> Specifically it's in src/switch_utils.c:1408 switch_find_local_ip()
> 
> Reading the code shows that setting the variables force_local_ip_v4 or force_local_ip_v6 will use the value you set instead of autodetecting, should you want to avoid the behaviour you've seen.
> 
> I'm not sure the origin of the IPv4 address, but the IPv6 one is one of the root DNS servers.
> 
> Looking at the source appears to confirm my previous statement... it creates a UDP socket and then calls connect to set the destination for packets, but it never actually sends any - just uses getsockname to see which IP it locally bound to.
> 
> -Steve
> 
> 
> On 24 March 2014 00:59, Steven Ayre <steveayre at gmail.com> wrote:
> Oh, and both IP and port are hardcoded in the source code.
> 
> 
> On 24 March 2014 00:58, Steven Ayre <steveayre at gmail.com> wrote:
> It's FreeSWITCH trying to automatically detect the ${local_ipv4} and ${local_ipv6} values.
> 
> It does this by attempting to send a packet to an IP it knows will have to go over the Internet and seeing which local IP the packet would leave the machine from. That means if you have multiple IPs assigned to your machine it'll know which one will send via the default gateway. That handles the simple single-homed case anyway.
> 
> It doesn't really matter whether NAT happens or not, it works just as well if your machine is listening on the public IP natively.
> 
> It's just trying to auto-detect what IP you're most likely to be reachable on.
> 
> Try a packet trace... from memory it only creates the socket, doesn't actually send the packet (?). But I may be wrong there.
> 
> -Steve
> 
> 
> On 23 March 2014 02:32, Terry Barnum <terry at digital-outpost.com> wrote:
> While playing with freeswitch yesterday, Little Snitch reported
> that freeswitch immediately upon launch tries to establish a connection to 82.45.148.209 and 2001:503:ba3e::2:30 on port 4242.
> 
> A whois shows the ipv4 to be from Telewest Broadband in the UK.
> 
> The only port 4242 setting I find is in  conf/autoload_configs/event_multicast.conf.xml but for 225.1.1.1.
> 
> Blocking the connection prevents sofia from registering with flowroute so I'm curious what it is. I couldn't find any relevant search results.
> 
> FreeSWITCH Version 1.5.11b+git~20140301T003717Z~f2331de68b~64bit (git f2331de 2014-03-01 00:37:17Z 64bit)
> 
> Thanks,
> -Terry
> _________________________________________________________________________
> Professional FreeSWITCH Consulting Services:
> consulting at freeswitch.org
> http://www.freeswitchsolutions.com
> 
> 
> 
> 
> Official FreeSWITCH Sites
> http://www.freeswitch.org
> http://wiki.freeswitch.org
> http://www.cluecon.com
> 
> FreeSWITCH-users mailing list
> FreeSWITCH-users at lists.freeswitch.org
> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
> http://www.freeswitch.org
> 
> 
> 
> _________________________________________________________________________
> Professional FreeSWITCH Consulting Services:
> consulting at freeswitch.org
> http://www.freeswitchsolutions.com
> 
> 
> 
> 
> Official FreeSWITCH Sites
> http://www.freeswitch.org
> http://wiki.freeswitch.org
> http://www.cluecon.com
> 
> FreeSWITCH-users mailing list
> FreeSWITCH-users at lists.freeswitch.org
> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
> http://www.freeswitch.org




Join us at ClueCon 2013 Aug 6-8, 2013
More information about the FreeSWITCH-users mailing list