Ramesh, NAT, issues can be complex set of variables, which is why I suggested we talk on air. That said, here are the key sip parameters for traversing nat.. sip.conf [general] canreinvite=nonat nat=yes localnet = <net ip of node>. ; typically something like 192.168.1.0/255.255.255.0 One of either externalip = <ip address>. ; this is your ISP provided ip address on the outside edge of the firewall. -or- externalhost = <fully qualified dns host name>. ; e.g. mynode.mydomain.ca Cheers, /Scott VE3ZTZ ————— iThing: Big thumbs & little keys. Please excuse typo, spelling and grammar errors • Good planets are hard to find – think before you print • My desire to be well-informed is currently at odds with my desire to remain sane. • Last night I played a blank CD at full blast. The Mime next door went nuts. On 2012-10-21, at 21:07, "Ramesh Dhami (VA3UV)" <Ramesh@va3uv.com> wrote:
Hi Guys;
I have a node behind a NAT router, which is also masquerading the incoming IP.
So any attempt to connect to it fails since the reported IP (i.e., the masqueraded IP) does not match the real IP (in the rpt_extnodes file).
I do not have access to the router at the site, so anything I can do on the node to make this work?
TIA!
Ramesh.
www.freestar.us _______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users