<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>I guess I should not take for granted very many things on this
but neither should anyone else.</p>
<p>Let me state something that everyone should realize but perhaps
does not with ASL nodes at 'home' with echolink.</p>
<p>Your cellphone equipped with echolink should NOT be set to ''run
echolink in the background'' when you are at home and connected to
the same wifi that your echolink node is. (you could turn your
wifi off on your phone and wait 15m+)<br>
</p>
<p>So when you come home, and echolink is really still running in
the background,</p>
<p>and your phone sees that you are connectable to your home
network.</p>
<p>It does connect to your wifi automatically and with echolink
running in the background, it creates a port clash. And your not
even using it. Even with proper port forwarding. And you will
think it is your ISP. Works sometimes and not others.<br>
</p>
<p>Simple as that. The default set-up is to run in the background
just like wifi to connect automatically when it hears it.<br>
</p>
<p>It does not matter that one is a '-L' or '-R' and the other is
personal call. 'cause they are trying to use the same ports.</p>
<p>Think about that the next time you troubleshoot one ! <br>
</p>
<p><u>It really should be the first thing looked for in home
asl/echolink node connectivity</u>.<br>
</p>
<p>For all the years I have been subscribed reading this list, I
have watched EL be the number one trouble on this list, again and
again and this is the root of most of it with 'home nodes'. But it
is just simple networking overlooking all that is happening behind
the nat.</p>
<p>So there you go... one good instance to have a node in the
cloud/vps. LOL</p>
<p>Have a great Holiday Weekend !<br>
</p>
<p>...mike/kb8jnm</p>
</body>
</html>