Subj : Re: Routing Problem
To : Mvan Le
From : Dale Shipp
Date : Tue Jan 01 2008 01:10 am
-=> On 12-31-07 02:19, Mvan Le <=-
-=> spoke to Dale Shipp about Re: Routing Problem <=-
ML> Ok. Based on the information above,
ML> 01130064.flo
ML> means you're trying to send a "Normal" flavoured packet to
ML> 3:275/100 (the "01130064" part of 01130064.flo is 3275100
ML> in hex, and the ".flo" part of 01130064.flo in Binkley-
ML> style outbound filenames means Normal routed mail).
Took me a while to figure out how you got that. 0x113 = 275 and
0x064 = 100. Not sure where the 3 came from. The node the netmail
was addressed to was 1:275/100. That netmail was still sitting there
tonight. I had to readdress it using the Argus interface to make it
get routed to 1:123/500 -- which is how my ROUTE.CFG file says should
happen to almost all netmail. The fact that it does not get addressed
to 1:123/500 is the problem.
ML> Argus should automatically send your net netmail packets
ML> (ie. the filename listed within the .clo file).
Before I made Argus readdress it, I also tried to change the flavor to
crash. That caused Argus to attempt a poll to
f100.n275.z1.fidonet.org. I'm uncertain how that could have worked
since 1:275/100 is PVT and that DNS does not exist.
ML> Hence we would focus troubleshooting efforts on your BBS
ML> and Squish, in which case post the contents of your
ML> route.cfg file.
My route.cfg file has a lot of standard comments in it. Here is what
remains after they are removed:
Send Normal World
Route normal 1:123/500 1:All 2:All 3:All 4:All 5:All
6:ALL
Send Crash 1:140/1
Send Crash 1:261/1
Send Crash 1:261/38
Send normal 1:123/500
I have tried altering the order, and changing the flavor to 1:123/500 to
crash instead of normal the two times it appears. No effect on
behavior -- mail still gets stuck without being routed.
Dale Shipp
fido_261_1466 (at) comcast (dot) net
(1:261/1466)
... Shipwrecked on Hesperus in Columbia, Maryland. 01:27:00, 01 Jan 2007
___ Blue Wave/DOS v2.30
