Subj : Re: Binkley
To : Marcin Gondek
From : Paul Quinn
Date : Thu Jul 05 2001 04:00 pm
Hi! Marcin,
On 04 Jul 01 22:48, Marcin Gondek wrote to Paul Quinn:
MG> My route.fe file
MG> === Begin ROUTE.FE ===
[ ...trim.. ]
MG> === End ROUTE.FE ===
I'm not a routing expert, but I had a long look at yours and saw some
redundancy. Keep in mind that the routing file is read by FE, top-down, so
that the last statement to mention a node or wildcard will affect its routing.
Here's what I recommend:
=== Begin ROUTE.FE ===
; Other zones routing:
Route-to 2:480/112 1:* 4:* 5:* 6:* 2:*
Route-to 2:2432/200 3:*
; MyZone routing (these are exceptions to the first line):
Route-to 2:467/70 2:460/* 2:4600/*
Route-to 2:467/70 2:461/* 2:4613/* 2:4614/* 2:4615/* 2:4616/*
Route-to 2:467/70 2:462/* 2:4621/* 2:4623/* 2:4624/* 2:4625/* 2:4626/* 2:4627/*
Have a good look and see what you think. I would welcome comments from others
as well. As I say, I'm no expert, and, I haven't had a lot of experience with
large routing systems.
As an afterthought: if your echomail is flowing well through Argus, then you
may be looking for something that isn't supposed to happen. When FE packs
either local or in-transit netmail, it will use an existing mail packet if one
exists already for an up/down-link. Have you got an arcmail packet viewer like
InspectA, so that you can view the contents of your outbound arcmail? Perhaps
your packed netmails have been packed-up in them, and you're looking for
newly-created arcmail bundles that aren't supposed to be there. :-)
Cheers,
Paul.
--- BT-W32 2.60XEg6/BinkD-W32 0.9.4
* Origin: Damn it! I wanna be _their_ aliens. (ZMH only) (3:640/384)
