<!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>
OK Barry, I now believe I see the distinction...<BR>
Check me out?<BR>
<BR>
On Mon, 2006-07-24 at 15:06 -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">></FONT>SNIP<
<FONT COLOR="#000000">> I have not thought this through fully yet (I admit)...</FONT>
<FONT COLOR="#000000">There was a time when using a NOS or Unix/Linux machine to implement</FONT>
<FONT COLOR="#000000">a "software solution" to implement NAT was the only way you could get</FONT>
<FONT COLOR="#000000">a single IP address user account to service more than a single client</FONT>
<FONT COLOR="#000000">machine behind it but today, the consumer IP/NAT routing appliance is</FONT>
<FONT COLOR="#000000">so commonly available that it is somewhat of a no-brainer whether or</FONT>
<FONT COLOR="#000000">not to use one.</FONT>
</PRE>
</BLOCKQUOTE>
Now this is how I see your LinkSys solution as applied to an existing Linux jnos install:<BR>
A) remove the tun device<BR>
b) attach a spare eth(1?) to the jnos stack<BR>
c) attach the LinkSys INTERNET to the eth(1?) interface (external modem presumed)<BR>
d) configure NAT & Firewall to interface to 44... static IP of jnos<BR>
e) attach the LinkSys LAN to the host eth(0?) interface<BR>
f) attach the remaining LAN ports to other hosts and also to the other internet bridge containing DSL or CABLE etc interface.<BR>
g) route as appropriate...<BR>
<BR>
Interesting concept - I doubt I would have tumbled to this on my own...
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000">The other thing that using an IP/NAT router in this configuration</FONT>
<FONT COLOR="#000000">does for you (particularly for those who are using cable internet</FONT>
<FONT COLOR="#000000">access) is that it eliminates the requirement that your NOS or</FONT>
<FONT COLOR="#000000">Unix/Linux machine, 1) have two interfaces in it in order to</FONT>
<FONT COLOR="#000000">accommodate a LAN "behind" your internet connection, and, 2) hear</FONT>
<FONT COLOR="#000000">all of those incessant ARP broadcasts on your "local" cable segment.</FONT>
<FONT COLOR="#000000">The amount of this traffic IS signficant (depending on the size of</FONT>
<FONT COLOR="#000000">your segment, of course) and using an IP/NAT router will completely</FONT>
<FONT COLOR="#000000">free your NOS or Unix/Linux machine from the resources it would have</FONT>
<FONT COLOR="#000000">to devote to hear all of these ARP broadcasts.</FONT>
</PRE>
</BLOCKQUOTE>
I never considered the Linux/jnos box as the internet gateway - although there is a great deal of press on the subject.<BR>
It seems like OLD 386/486 throw-aways make a "good" bridge/firewall as an alternative to a LinkSys appliance.<BR>
I do now wonder if adding jnos to this incoming bridge thus expanding it to Internet + RF paths makes sense?<BR>
The device needs no operator interface since everything may be doable remotely via telnet - ssh - etc...<BR>
This one for another day?<BR>
<BR>
Thanks for the concept Barry, I may already have all the hardware to try this out for kicks.<BR>
As an aside: you notice that Maiko has begun the process of detaching jnos/host support routines/libraries?<BR>
It may be a future strategy of his that NAT can be "plugged in" when needed and not included into the application?<BR>
Our conversation here may become the "old way" of doing things...<BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
<PRE>
<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>