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
Gosh.. just buy an RTCM, and you wont have problems like that ;-)... [Eventually Ya'all will realize that I'm going to sarcastically suggest fixing just about EVERYTHING and ANYTHING with an RTCM].... Jim
Date: Sun, 21 Oct 2012 21:06:59 -0400 From: Ramesh@va3uv.com To: app_rpt-users@ohnosec.org Subject: [App_rpt-users] Node behind a NAT router
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
Does the RTCM work with XIPAR? If it does I haven't figured it out yet (which isn't saying much). jeff ________________________________ From: app_rpt-users-bounces@ohnosec.org [mailto:app_rpt-users-bounces@ohnosec.org] On Behalf Of Jim Duuuude Sent: Sunday, October 21, 2012 7:18 PM To: Ramesh Dhami; app_rpt mailing list Subject: Re: [App_rpt-users] Node behind a NAT router Gosh.. just buy an RTCM, and you wont have problems like that ;-)... [Eventually Ya'all will realize that I'm going to sarcastically suggest fixing just about EVERYTHING and ANYTHING with an RTCM].... Jim
Date: Sun, 21 Oct 2012 21:06:59 -0400 From: Ramesh@va3uv.com To: app_rpt-users@ohnosec.org Subject: [App_rpt-users] Node behind a NAT router
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
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
Hi Scott; Thanks! - I know about the nat=yes parameter for SIP connections... but not sure if app_rpt supports this or whether the same can be applied for inbound IAX connections. I'm busy with work stuff tonight and got busy with some D-STAR (FREE STAR*) stuff last night, hence couldn't commit to chatting with you. I used to take my FM portable to work (I work very close to YYZ... in fact, one of my offices overlooks the YYZ stack!). May be we can chat via phone tomorrow? Ramesh. On 22/10/2012 7:26 PM, S. Scott wrote:
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
participants (4)
-
Jeffrey S. Carrier -
Jim Duuuude -
Ramesh Dhami (VA3UV) -
S. Scott