<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<META NAME="Generator" CONTENT="MS Exchange Server version 14.02.5004.000">
<TITLE>My dumb question of the day</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->
<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Calibri">So how do you connect your Allstar node to your Echolink node - when you are behind a firewall.</FONT></SPAN></P>
<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Calibri">For example… my external ip address is 24.xx.</FONT></SPAN><SPAN LANG="en-us"><FONT FACE="Calibri">xx.xx (a public address to the internet world). my allstar server which has my echolink node on it, it on a private address of 192.168.xx.xx. There is a Nat between the 2. When I try to connect my allstar node on the same server to my echolink node, I get a connection failed because it tried to connect to the 24.xx.xx.xx address which it can't see. </FONT></SPAN></P>
<P DIR=LTR><SPAN LANG="en-us"></SPAN></P>
<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Calibri">I'll go see if my router has the ability to spoof that address as some do</FONT></SPAN><SPAN LANG="en-us"><FONT FACE="Calibri">. I can't believe I'm the only one that might have experienced this problem. Just curious how others have remedied it…</FONT></SPAN></P>
<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Calibri">Alan</FONT></SPAN><SPAN LANG="en-us"></SPAN></P>
</BODY>
</HTML>