Subj : Re: Routing Problem
To   : Mvan Le
From : Dale Shipp
Date : Sat Jan 05 2008 11:05 pm

 -=> On 01-05-08  21:47,  Mvan Le <=-
 -=> spoke to Dale Shipp about Re: Routing Problem <=-

  I think that we have a mis-understanding of what I have been asking
  and the intent of what I wish to happen.   Much of what you said makes
  sense, and would allow my Argus to send direct to multiple nodes if
  that is what I desired -- but it is not what I desire.

 ML> Otherwise you will need to manually define a node & IP entry for
 ML> 1:275/100  (et al) in Argus configuration so that if it finds a file 
 ML> named 01130064.*o it will know where to send it. 

   I have done that for a few nodes -- but the whole point of my
   starting this discussion was that I want mail destined for any other
   node to be routed out through 1:123/500.   That is not happening, no
   matter how I twiddle with the ROUTE.CFG that Squish is supposed to
   look at.


 DS> My route.cfg file has a lot of standard comments in it.   Here is
 DS> what remains after they are removed:
 
 DS> Send Normal World
 DS> Route           normal   1:123/500 1:All 2:All 
 DS> 3:All 4:All 5:All 6:ALL
 DS> Send            Crash   1:140/1
 DS> Send     Crash   1:261/1
 DS> Send            Crash   1:261/38
 DS> Send            normal   1:123/500
 
 DS> I have tried altering the order, and changing the flavor to 1:123/500
 DS> to crash instead of normal the two times it appears.   No effect on
 DS> behavior -- mail still gets stuck without being routed.

 ML> Order is important. 

 ML> Try this,

 ML> =================
 ML> Send Normal World
 ML> #End Route.Cfg
 ML> =================

 ML> Ie. "Send Normal World" is the only command you need. You 
 ML> don't need all the other Send commands unless you want to 
 ML> specifically alter the flavour of the packet for those 
 <node> <nodes ...> (in this case netmail message), for 
 ML> example when you're a NC or hub and want to alter passthru 
 ML> messages. 

  The problem is that I do want to alter the routing (not the flavor) of
  packets for all other nodes not explicitly mentioned.

 ML> The way you currently have Route.Cfg set up, ie. 

 ML> ==============================================
 ML> Send Normal World
 ML> Route           normal   1:123/500 1:All 2:All 
 ML> 3:All 4:All 5:All 6:ALL
 ML> Send            Crash   1:140/1
 ML> Send     Crash   1:261/1
 ML> Send            Crash   1:261/38
 ML> Send            normal   1:123/500
 ML> ==============================================

 ML> All your mail is getting re-addressed to 1:123/500, so the 
 ML> other Send commands have no effect.

  But the point is that it is *not* getting re-addressed to 1:123/500 as
  I intend to happen.

 ML> Anyway, your problem is to do with Argus. You need to define the
 ML> destination  node & IP addresses in Argus. If it doesn't know about the
 ML> destination, your packet will just get stuck in the 
 ML> outbound directory. And check that the crash netmail 
 ML> message is created in your outbound directory with *.cut 
 ML> extension.

  The destination node and IP address for 1:123/500 is defined in Argus.
  The others are not, because I do not intend for mail to be sent
  directly to them -- rather I intend for it to be routed through
  1:123/500.




.... Shipwrecked on Hesperus in Columbia, Maryland. 23:18:15, 05 Jan 2007
___ Blue Wave/DOS v2.30

--- Maximus/NT 3.01
 * Origin: Owl's Anchor (1:261/1466)

.