<!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.12.3">
</HEAD>
<BODY>
On Tue, 2007-04-17 at 12:08 -0500, Barry Siegfried wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000">["(Skip) K8RRA" <<A HREF="mailto:k8rra@ameritech.net">k8rra@ameritech.net</A>> wrote]:</FONT>
<FONT COLOR="#000000">> Try this model:</FONT>
<FONT COLOR="#000000">> Site A (me):</FONT>
<FONT COLOR="#000000">> Host A1 / Linux: static 192.168.1.32 IP + jnos 44.102.132.20</FONT>
<FONT COLOR="#000000">> LAN to Internet bridge appliance: LAN IP 192.168.1.254 + WAN IP 24...</FONT>
<FONT COLOR="#000000">> dynamic</FONT>
<FONT COLOR="#000000">> Host A2 / any O/S: dynamic LAN IP 192...</FONT>
<FONT COLOR="#000000">And don't you also have a 44-net IP address on the Linux side of</FONT>
<FONT COLOR="#000000">the TUN device to JNOS?</FONT>
</PRE>
</BLOCKQUOTE>
Oh no - the host stack only has a route to 44... network - there is no 44 IP on the host.
<BLOCKQUOTE TYPE=CITE>
<PRE>
<<SNIP>><FONT COLOR="#000000">- the primary issue is that the FROM IP is NOT 44....</FONT>
<FONT COLOR="#000000">Well it should be. Why isn't it</FONT>?
</PRE>
</BLOCKQUOTE>
No - it should not be - network rules are being accurately followed here.<BR>
The only way to get to 44... as a FROM IP (without re-writing jnos to share the host stack) is thru NAT as far as I know.<BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000">> As a parting thought Barry:</FONT>
<FONT COLOR="#000000">></FONT>
<FONT COLOR="#000000">> Remember this conversation is pointed at defining a *representative*</FONT>
<FONT COLOR="#000000">> set of configuration examples for documentation on the wiki. It is</FONT>
<FONT COLOR="#000000">> my desire that the wiki example might be used like a cut-and-paste</FONT>
<FONT COLOR="#000000">> to create new config files while changing a site.</FONT>
<FONT COLOR="#000000">Skip, I'm sorry to tell you that cutting and pasting other people's</FONT>
<FONT COLOR="#000000">configs are EXACTLY what gets most newbies into trouble and getting</FONT>
<FONT COLOR="#000000">other people involved anyway "to straighten out the mess". You are</FONT>
<FONT COLOR="#000000">not the first person to try and do this with an "automated installation"</FONT>
<FONT COLOR="#000000">of one sort or another. All very noble goals to get more people</FONT>
<FONT COLOR="#000000">"interested". But it doesn't change the fact that every config is</FONT>
<FONT COLOR="#000000">unique and there is just no way around that.</FONT>
<FONT COLOR="#000000">Honestly, I think you are spinning your wheels with this idea of</FONT>
<FONT COLOR="#000000">creating a "one config fits all" scenario.</FONT>
</PRE>
</BLOCKQUOTE>
Oh no no - not one but *maybe* a dozen...?<BR>
My life has demonstrated many times that learning from example is quite effective.<BR>
Please don't confuse "not thinking for one's self" with "cut-and-paste" - and I'll leave automation to developers.<BR>
I'm headed for enough examples that learning what is "right for me" can be done from comparison with what has been "right for several others".<BR>
That is why I ask you for examples of what has worked in the past...
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000"> There are infinite</FONT>
<FONT COLOR="#000000">possibilities within infinite choices.</FONT>
</PRE>
</BLOCKQUOTE>
Oh come on - only if you include minutia like specific IP numbers do the options count become truly large.<BR>
The sad part in this is that manufacturer and model of equipment does effect the options available to the user (as in LinkSys Router & Bridge appliance).<BR>
<BR>
Yup - havin fun.<BR>
<TABLE CELLSPACING="0" CELLPADDING="0" WIDTH="100%">
<TR>
<TD>
<BR>
73<BR>
de [George (Skip) VerDuin] K8RRA k
</TD>
</TR>
</TABLE>
</BODY>
</HTML>