<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.10.1">
</HEAD>
<BODY>
Hey Barry, kewl response.<BR>
<BR>
Allow me to begin by focus on your last thought "absolutely NOTHING"...<BR>
My vision is to establish a parallel path to say your home internet presence for multiple services like SMTP, ftp, http, (etc?).<BR>
Path 1 is from my LAN workstation out the dsl bridge now in place - and as you see it works OK in client-server mode.<BR>
Path 2 is from my LAN workstation out the (jnos?) bridge over 44... now in place - and you see it fails (I can't ping you).<BR>
Path 2 has LONG latency and will not be chosen until path 1 dies - kewl way to run a redundant network.<BR>
<BR>
What gets in the way is that my jnos path does not NAT.<BR>
So the solution options under consideration below:<BR>
<BR>
On Sat, 2006-07-22 at 12:14 -0400, Barry Siegfried wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000">["George (Skip) VerDuin" <<A HREF="mailto:k8rra@ameritech.net">k8rra@ameritech.net</A>> wrote]:</FONT>
<FONT COLOR="#000000">> The issue is: my jnos does not do NAT (Network Address Translation).</FONT>
<FONT COLOR="#000000">NAT *can* be incorporated into JNOS. NAT for xNOS was actually</FONT>
<FONT COLOR="#000000">developed a long time ago. It is simply a matter of somebody</FONT>
<FONT COLOR="#000000">wanting to take the time to port it into JNOS.</FONT>
</PRE>
</BLOCKQUOTE>
No demand? No action. That seems very normal.<BR>
Yet this seems to play heavily in the comparison of winlink to jnos without being focused on in the debate.
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000">> I've stumbled into a wide interest issue:</FONT>
<FONT COLOR="#000000">></FONT>
<FONT COLOR="#000000">> All you guys discussing IP over AX.25 - have you included ARP as</FONT>
<FONT COLOR="#000000">> a part of overhead in your considerations?</FONT>
<FONT COLOR="#000000">ARP is a necessary part of any "broadcast" implementation of the</FONT>
<FONT COLOR="#000000">link layer. It is the only way to translate MAC (physical or</FONT>
<FONT COLOR="#000000">callsign) "addresses" into IP addresses.</FONT>
</PRE>
</BLOCKQUOTE>
Clearly. and without NAT it can't work for my configuration DESIRE.
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000">> All you guys discussing routing between jnos nodes mounted on</FONT>
<FONT COLOR="#000000">> 192.168.x.y private IP LANS have you considered NAT over RF?</FONT>
<FONT COLOR="#000000">All you guys discussing routing between jnos nodes mounted on</FONT>
<FONT COLOR="#000000">private LANS have you considered configuring the LAN as part of</FONT>
<FONT COLOR="#000000">the amprnet? </FONT>
</PRE>
</BLOCKQUOTE>
Clearly a routing solution. I suspect it becomes unmanageable to administer such a beast internationally.<BR>
As an example: <BR>
I'm now assigned 44.102.132.20 for say 6 months - but I'm not installed into DNS yet so you will not find k8rra.ampr.org.<BR>
Whereas this situation is manageable today, consider applying it under emergency conditions when you might NEED to find k8rra....<BR>
I believe private LANs and NAT offers a more manageable approach - not perhaps ideal.
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000">This can be done to the extent that individual</FONT>
<FONT COLOR="#000000">machines on your LAN can be made as "public" or "private" as you</FONT>
<FONT COLOR="#000000">want them to be by some simple IP routing manipulation in them</FONT>
<FONT COLOR="#000000">and in the IP/NAT router and also with the proper configuration</FONT>
<FONT COLOR="#000000">of an IPIP (or IPUDP) encapper as a "public" member of your LAN.</FONT>
</PRE>
</BLOCKQUOTE>
I need to know more engineering behind this and I expect to over time...
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000">> Other solutions than NAT? Yes potentially. ENCAP comes to mind,</FONT>
<FONT COLOR="#000000">> but I have not got a working example yet. NAT as a solution?</FONT>
<FONT COLOR="#000000">In my own experience what seems to work best is a delicate combination</FONT>
<FONT COLOR="#000000">of NAT (in a commercially available IP/NAT router) AND IPIP (or IPUDP)</FONT>
<FONT COLOR="#000000">encapsulation to handle the "public" reachability of 44-net.</FONT>
</PRE>
</BLOCKQUOTE>
This suggests that NAT applied to RF links is a bad solution? OK let me think this over?
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000">[snip]</FONT>
<FONT COLOR="#000000">> Now I don't know if there is a solution to my desire.</FONT>>SNIP<<FONT COLOR="#000000"> I guess what I am not understanding</FONT>
<FONT COLOR="#000000">is what you are trying to accomplish for which you can't find the</FONT>
<FONT COLOR="#000000">solution.</FONT>
</PRE>
</BLOCKQUOTE>
Does this further information muddy the water?
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000">> As far as a solution to my desire? - I'm beginning to classify it as</FONT>
<FONT COLOR="#000000">> "pie in the sky"...</FONT>
<FONT COLOR="#000000">There is absolutely NOTHING you cannot do without the right software</FONT>
<FONT COLOR="#000000">and some proper planning and configuration.</FONT>
<FONT COLOR="#000000">73, de Barry, K2MF >></FONT>
<FONT COLOR="#000000"> o</FONT>
<FONT COLOR="#000000"> <|> Barry Siegfried</FONT>
<FONT COLOR="#000000">+---------/-\---------------------------+</FONT>
<FONT COLOR="#000000">| Internet | <A HREF="mailto:bgs@mfnos.net">bgs@mfnos.net</A> |</FONT>
<FONT COLOR="#000000">| HomePage | <A HREF="http://www.mfnos.net/~bgs">http://www.mfnos.net/~bgs</A> |</FONT>
<FONT COLOR="#000000">+----------+----------------------------+</FONT>
<FONT COLOR="#000000">| Amprnet | <A HREF="mailto:k2mf@nnj.k2mf.ampr.org">k2mf@nnj.k2mf.ampr.org</A> |</FONT>
<FONT COLOR="#000000">| PBBS | k2mf@k2ge.#cnj.nj.usa.noam |</FONT>
<FONT COLOR="#000000">+----------+----------------------------+</FONT>
<FONT COLOR="#000000">_______________________________________________</FONT>
<FONT COLOR="#000000">nos-bbs mailing list</FONT>
<FONT COLOR="#000000"><A HREF="mailto:nos-bbs@lists.tapr.org">nos-bbs@lists.tapr.org</A></FONT>
<FONT COLOR="#000000"><A HREF="https://lists.tapr.org/cgi-bin/mailman/listinfo/nos-bbs">https://lists.tapr.org/cgi-bin/mailman/listinfo/nos-bbs</A></FONT>
</PRE>
</BLOCKQUOTE>
<TABLE CELLSPACING="0" CELLPADDING="0" WIDTH="100%">
<TR>
<TD>
<BR>
73<BR>
de Skip k8rra k<BR>
<BR>
<BR>
</TD>
</TR>
</TABLE>
</BODY>
</HTML>