Subj : Problem at your system
To : deon
From : Andrew Leary
Date : Mon Jan 23 2023 12:47 am
Hello deon!
23 Jan 23 11:34, you wrote to Ward Dossche:
de> Sorry, pressed send by mistake:
>> I was wrong...
>> Ward, I didnt read my dump fully.
>>
>> Ward, it does appear to be your system, that is addressing the
>> "packet" to Paul at 3:770/1, but the "netmail" inside the packet
>> file, is addressed to "2/3".
>>
>> So it would appear to be from your side...
de> More info, for those interested:
de> A packet message starts after the packet header (which finishes at
de> 0x3a) and starts with 0x02 0x00 (FTS-0001.16)
de> Ward, it seems you are packing the message incorrectly.
Confirmed here on my D'Bridge 4 (01-01-2023) test point; I created a message
addressed to Ward in the D'Bridge editor, saved it, and quit back to D'Bridge.
The message was packed for 2:292/854 in the queue. I then quit out of
D'Bridge and examined the .PKT file in D'Bridge's queue directory. The packet
header was addressed to 2:292/854, but the message was addressed to 1:1/2 with
the INTL kludge indicating 2:292/854 as the ultimate destination.
It appears that the version of D'Bridge 4 that Ward is using (01-01-2023?) is
packing messages as if they were to be sent through a zonegate. The packet
header is properly addressed to the destination, but the message(s) in the
packet are addressed to the zonegate address. This appears to happen
regardless of whether or not you select the "Use Zonegate" flag in D'Bridge's
editor. It also seems to happen even on messages flagged as Crash or Direct.