[ previous ] [ next ] [ threads ]
 To :  "yate" <yate@v...>
 From :  "cc08" <cc08@r...>
 Subject :  Re: [yate] Problem with NAT
 Date :  Wed, 16 Nov 2011 09:49:59 +0400
Hi, Paul!

Take a look at this issue more widely.
For example I have a situation where private addresses are routed along the 
public address without NAT.
So to say the specifics of small campus networks.
If you do not mind, can upgrade a little logic ysipchan, like so:

In ysipchan.conf, add section
[like adresses_without_nat]

In ysipchan.cpp, rewrite function:
static bool isPrivateAddr(const String& host)
// todo to handle list of excludes

Or to list wish features ?

with best regards...

>Found the problem!
>The 1.x.y.z addresses you have inside the NAT are public routable addresses
>(belong to APNIC) so Yate has no hint a NAT is involved.
>Yate assumes a NAT exists when a private address appears in Contact but the
>request was received from a public IP. A simple difference in IP address is
>not enough as it can be caused by factors as SIP proxies and/or asymmetric
>The private address ranges are:
> - (MS APIPA)
> -
> -
> -
>Please change the LAN addresses to one of the 3 ranges above at there are 
>applications that would take that as a strong hint of not being routable 
>Internet. Besides that you must never conflict with officially allocated
>On Thursday 10 June 2010 11:50:16 am Alfred Stainer wrote:
>> Hi Paul,
>> I have Yate directly connected to internet and 2 phones to my home 
>> connected
>> to internet (my ISP offers ADSL behind a NAT).
>> There is no Gateway between Yate and phones.
>> I have attached to this email original .pcap files.
>> Can be the problem due to the IP assigned to my phones by my ISP?
>> Thanks,
>> Alfred