<!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>
OK Jay - Barry says I am proving *his* point with *my* argument...<BR>
Now you pull out this black magic book from somewhere and make sense of it all...<BR>
<BR>
On Tue, 2007-04-17 at 15:03 -0400, Jay Nugent wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000">Greetings Skip (et al),</FONT>
<FONT COLOR="#000000">On Tue, 17 Apr 2007, (Skip) K8RRA wrote:</FONT>
<FONT COLOR="#000000">> On Tue, 2007-04-17 at 12:08 -0500, Barry Siegfried wrote:</FONT>
</PRE>
</BLOCKQUOTE>
<BR>
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000"> The "source" address of an outgoing packet is determined by the</FONT>
<FONT COLOR="#000000">*interface* address used. And which *interface* is determined by the</FONT>
<FONT COLOR="#000000">destination address you are trying to reach, and what *interface* the</FONT>
<FONT COLOR="#000000">*route table* says you must use to get to the desired destination.</FONT>
</PRE>
</BLOCKQUOTE>
I did not find this in the man pages - it's good stuff.
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000"> That's alot to chew on. Let me explain...</FONT>
<FONT COLOR="#000000"> I have a Linux box here. It's address is 216.144.208.6. However, I </FONT>
<FONT COLOR="#000000">would like this box to also be able to reach the HTTP webpages at </FONT>
<FONT COLOR="#000000">wb8rcr.ampr.org. To do this I added an additional *interface* to this box </FONT>
<FONT COLOR="#000000">along with the supporting *route* entry, as follows:</FONT>
<FONT COLOR="#000000"> ifconfig eth0:44 44.102.1.2</FONT>39
</PRE>
</BLOCKQUOTE>
What black magic is this ":44" stuff? does this make your eth0 interface carry a special (alias?) *44*?<BR>
May I presume the (non-alias?) ifconfig for eth0 carries the 216.144.208.6?
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000"> route add -net 44.0.0.0/8 gw 44.102.1</FONT>.1
</PRE>
</BLOCKQUOTE>
Isn't the route statement missing the interface "dev eth0:44" spec?<BR>
Or is :44 a subnet spec?<BR>
<BR>
I recognize 44.102.1.1 - is it a separate dos platform on the LAN with jnos?<BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000"> BINGO!!!</FONT>
</PRE>
</BLOCKQUOTE>
BINGO indeed...
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000">Now when I point my browser to <A HREF="http://wb8rcr.ampr.org">http://wb8rcr.ampr.org</A>,</FONT>
</PRE>
</BLOCKQUOTE>
Resolved thru DNS by virtue of ampr.org registration as shown in HOSTS table you keep on DRG?
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000"> my</FONT>
<FONT COLOR="#000000">packets to out addressed TO 44.102.200.17, addressed FROM 44.102.1.239. </FONT>
<FONT COLOR="#000000">They are 'GW'ayed to the JNOS/Hamgate 44.102.1.1, who then passes them</FONT>
<FONT COLOR="#000000">through the normal AMPRnet routing to get to wb8rcr.ampr.org's web server.</FONT>
</PRE>
</BLOCKQUOTE>
Whew - Ola / no NAT!
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000"> When the wb8rcr.ampr.org web server responds, it returns packets</FONT>
<FONT COLOR="#000000">addressed to my FROM address of 44.102.1.239. Following the normal</FONT>
<FONT COLOR="#000000">AMPRnet network routing that says send all 44.102.1/24 to</FONT>
<FONT COLOR="#000000">Hamgate.Washtenaw.AMPR.org (44.102.1.1).</FONT>
<FONT COLOR="#000000"> Normally, Hamgate.Washtenaw sends all 44.102.1/24 traffic out its RF</FONT>
<FONT COLOR="#000000">port, but remember we put in a /32 route stipulating we are to send</FONT>
<FONT COLOR="#000000">44.102.1.239 out the ethernet. So "Thinking like a Packet" we do just</FONT>
<FONT COLOR="#000000">that and the web content reaches my Linux box and my browser dislays the</FONT>
<FONT COLOR="#000000">webpage :)</FONT>
<FONT COLOR="#000000"> Forget NAT (it's almost as evil as firewalls are). We have enough</FONT>
<FONT COLOR="#000000">44-net addresses to go around so there is NO need to use NAT anywhere. </FONT>
<FONT COLOR="#000000">If you want more 44-et addresses Skip, fill out the application on the</FONT>
<FONT COLOR="#000000">MI-DRG.org website and get a few more assigned to you.</FONT>
</PRE>
</BLOCKQUOTE>
If I understand, then that will be one 44.. per box on the LAN having access thru hamgate.
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000"> Also, there is</FONT>
<FONT COLOR="#000000">nothing "magical" about the 44-net addresses. ANY ip address *can* be</FONT>
<FONT COLOR="#000000">routed over the RF network. We *could* be using 192.168.x.y if we wanted. </FONT>
<FONT COLOR="#000000">Just so long as the ROUTING TABLES on every node that needs to pass such</FONT>
<FONT COLOR="#000000">traffic knows how to send them. They are *just numbers*</FONT>.
</PRE>
</BLOCKQUOTE>
Well sorta yes - but...<BR>
When I read the "beauty" of 192.168 I interpret it to imply "freedom to choose subnet members with impunity".<BR>
The private subnets manage their own IP assignments without concern for the rest of the world and insulate themselves with NAT.<BR>
With the above approach to the private C routing, no one else had better duplicate my choice of node IP addresses.<BR>
I'm concerned that use of *just numbers* approach creates an unmanageable circumstance...? (more later eye-to-eye)
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000"> Skip, I believe you will be attending this Saturday's DRG meeting? In</FONT>
<FONT COLOR="#000000">my training session I'll be going over static routing and how to "Think</FONT>
<FONT COLOR="#000000">like a Packet".</FONT>
</PRE>
</BLOCKQUOTE>
I saw the agenda - it looks very meaty...
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000"> Hope to see you there!</FONT>
</PRE>
</BLOCKQUOTE>
And I *pray* that you will work with me to get at least one topic from the agenda also presented thru wiki.<BR>
I *really want* to present wiki in the context: "You can see this (some) topic already presented here another way / here is the example..."<BR>
HOW CAN I HELP MAKE THAT HAPPEN?
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000"> And hope that we can help clear</FONT>
<FONT COLOR="#000000">up any misconceptions and help lift the fog a little. I'll bring an empty</FONT>
<FONT COLOR="#000000">V8 juice can with me so you can smack it into your forehead when this all</FONT>
<FONT COLOR="#000000">comes clear for you ;-)</FONT>
</PRE>
</BLOCKQUOTE>
I'm already wet!
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000"> See you there!</FONT>
<FONT COLOR="#000000"> --- Jay Nugent WB8TKL</FONT>
<FONT COLOR="#000000"> </FONT>
</PRE>
</BLOCKQUOTE>
<BR>
<TABLE CELLSPACING="0" CELLPADDING="0" WIDTH="100%">
<TR>
<TD>
<BR>
73<BR>
de [George (Skip) VerDuin] K8RRA k
</TD>
</TR>
</TABLE>
</BODY>
</HTML>