<!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>
Thanks so much Glenn, I believe your experience leads to my underlying issue.<BR>
The issue is: my jnos does not do NAT (Network Address Translation).<BR>
<BR>
I've stumbled into a wide interest issue:<BR>
All you guys discussing IP over AX.25 - have you included ARP as a part of overhead in your considerations?<BR>
All you guys discussing routing between jnos nodes mounted on 192.168.x.y private IP LANS have you considered NAT over RF?<BR>
<BR>
I believe this is how my issue plays out on this thread:<BR>
When I ping from jnos, I ping from a 44... IP and everything is kewl.<BR>
When I ping from jnos host, I ping from a 192... IP and the remote jnos routes the ICMP to it's own 192... IP LAN rather than back to me.<BR>
The proof of that requires a trace from the remote jnos - something I don't have in hand.<BR>
The trace I have of my own node demonstrates however that NAT is not in use, <BR>
and therefore the 192... (from IP) is being placed in the RF packet <BR>
and the "Echo Response" ICMP packet carries the 192... in the "to" IP <BR>
and that does not initiate ARP to find my call from the remote node of jnos<BR>
and that does not route back to to my node.<BR>
<BR>
Other solutions than NAT? Yes potentially. ENCAP comes to mind, but I have not got a working example yet.<BR>
NAT as a solution? More in the next paragraph, but I found an interesting NAT & P2P piece on pg86 of August Linux Journal.<BR>
<BR>
>From day 1 (a long time ago) I considered winlink a very utilitarian half solution to remote (also as in emergency) communication.<BR>
>From day 2 (less long ago) I considered jnos an intriguing network alternative, enough so to put a fair amount of energy into understanding it.<BR>
[YES - more energy needed...]<BR>
Today I see no easy solution to my desire for an AX.25 (ham radio) path for TCP/IP traffic unless jnos is the source (still a half solution).<BR>
YES - SMTP will transport mail deposited into the jnos queue from 192... hosts, so I have again a half solution (perhaps good enough for now)...<BR>
YES - ftp will move binary files as long as jnos sysop console is the ftp initiator (another half solution)...<BR>
<BR>
Now I don't know if there is a solution to my desire.<BR>
I know that private LAN configurations in IPv4 is real convenient and global registration of IPs is not a solution I care to participate in.<BR>
If anyone sees an error in my analysis, I want to hear it.<BR>
As far as this thread on this reflector goes, my original premise that jnos acts as a bridge is wrong and I'm OK with that understanding.<BR>
As far as a solution to my desire? - I'm beginning to classify it as "pie in the sky"...<BR>
<BR>
<BR>
On Tue, 2006-07-18 at 14:22 -0700, Glenn Thomas wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000">Interesting observation...</FONT>
<FONT COLOR="#000000">I saw something similar years ago on a community NOS system that may </FONT>
<FONT COLOR="#000000">be related. The NOS system had RF ports on 144, 220 and 440. I would </FONT>
<FONT COLOR="#000000">occasionally lose my head and try to connect to it on 144. The issue </FONT>
<FONT COLOR="#000000">was that, in those days, the packet channel was overloaded. More </FONT>
<FONT COLOR="#000000">often than not the link would retry out. My next attempt to connect </FONT>
<FONT COLOR="#000000">was on 220, where the channel was essentially clear. The NOS system </FONT>
<FONT COLOR="#000000">apparently heard me because it responded - on 144! Apparently once it </FONT>
<FONT COLOR="#000000">heard a station on one port, it always responded to that station on </FONT>
<FONT COLOR="#000000">that port - even if the station moved to another port. This has the </FONT>
<FONT COLOR="#000000">same flavor as 'once the RF path is used that the "...$ ping ..." is </FONT>
<FONT COLOR="#000000">no longer useful'.</FONT>
<FONT COLOR="#000000">I dunno if this is the same issue - or even if my routing issue still </FONT>
<FONT COLOR="#000000">exists! (that was many years ago and far far away). This is just an </FONT>
<FONT COLOR="#000000">observation that may or may not be relevant...</FONT>
<FONT COLOR="#000000">73 de Glenn WB6W</FONT>
<FONT COLOR="#000000">WAR IS PEACE!</FONT>
<FONT COLOR="#000000">FREEDOM IS SLAVERY!</FONT>
<FONT COLOR="#000000">IGNORANCE IS STRENGTH!</FONT>
<FONT COLOR="#000000">(be seeing you!)</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>