[OpenSIPS-Devel] [opensips] NAT Via Test Failure (#401)
jalung
notifications at github.com
Mon Feb 2 15:54:28 CET 2015
Bogdan, the answer is yes to your first question.
I also tested whether check_ip_address() is returning 0 by adding open/close braces for each of the if/return 0 statements and placing a comment before the return statement and the comments do not print nor does function perform the final return -1 at the end. It silently dies there on some requests from the same dialog for that client in the example.
The loop in the ClientNatTest() indeed is stopped, because the check_ip_address() is hung/stopped. This may be a compiler/platform feature.
Some data for that:
INFO:nat_traversal:ClientNatTest: NAT test=1 src=xxx.xxx.xxx.xxx:8039
INFO:nat_traversal:rfc1918address: NAT NETADDR=16241
INFO:nat_traversal:ClientNatTest: NAT test=2 src=xxx.xxx.xxx.xxx:8039
INFO:nat_traversal:ClientNatTest: NAT test=1 src=xxx.xxx.xxx.xxx:8039
INFO:nat_traversal:rfc1918address: NAT NETADDR=16241
INFO:nat_traversal:ClientNatTest: NAT test=2 src=xxx.xxx.xxx.xxx:8039
INFO:nat_traversal:ClientNatTest: NAT test=1 src=xxx.xxx.xxx.xxx:8039
INFO:nat_traversal:rfc1918address: NAT NETADDR=16241
INFO:nat_traversal:ClientNatTest: NAT test=2 src=xxx.xxx.xxx.xxx:8039
INFO:nat_traversal:ClientNatTest: NAT test=1 src=xxx.xxx.xxx.xxx:8039
INFO:nat_traversal:rfc1918address: NAT NETADDR=16241
INFO:nat_traversal:ClientNatTest: NAT test=2 src=xxx.xxx.xxx.xxx:8039
INFO:nat_traversal:ClientNatTest: NAT test=1 src=xxx.xxx.xxx.xxx:8039
INFO:nat_traversal:rfc1918address: NAT NETADDR=16241
INFO:nat_traversal:ClientNatTest: NAT test=2 src=xxx.xxx.xxx.xxx:8039
INFO:nat_traversal:ClientNatTest: NAT test=1 src=xxx.xxx.xxx.xxx:8039
INFO:nat_traversal:rfc1918address: NAT NETADDR=16241
INFO:nat_traversal:ClientNatTest: NAT test=2 src=xxx.xxx.xxx.xxx:8039
INFO:nat_traversal:ClientNatTest: NAT test=1 src=xxx.xxx.xxx.xxx:8039
INFO:nat_traversal:rfc1918address: NAT NETADDR=16241
INFO:nat_traversal:ClientNatTest: NAT test=2 src=xxx.xxx.xxx.xxx:8039
INFO:nat_traversal:ClientNatTest: NAT test=1 src=xxx.xxx.xxx.xxx:8039
INFO:nat_traversal:rfc1918address: NAT NETADDR=16241
INFO:nat_traversal:ClientNatTest: NAT test=2 src=xxx.xxx.xxx.xxx:8039
INFO:nat_traversal:test_source_address: NAT different_ip=-1 via1_port=44043 different_port=1
INFO:nat_traversal:ClientNatTest: NAT success= 2
Indicates the client is trying until eventually test is successful, but client still not logged in.
In other tests such as a simple "whois" from the command line on the IP, it has an unusual delay before returning results.
---
Reply to this email directly or view it on GitHub:
https://github.com/OpenSIPS/opensips/issues/401#issuecomment-72469767
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/devel/attachments/20150202/73838918/attachment-0001.htm>
More information about the Devel
mailing list