Subj : Hi
To   : Deon George
From : mark lewis
Date : Thu Sep 06 2018 10:48 am


 On 2018 Sep 06 06:56:18, you wrote to Vince Coen:

 DG> Actually I have though. This example is for the 314 network (pinet) that I
 DG> am connected to. My Mystic IS set for 314:314/180.1, but packets sent to
 DG> MBSE (which is 314:314/180) appear to be from 314:65535/180.1.

 DG> The same is true for Fidonet Mystic IS configured for 3:633/509.1, but 
MBSE
 DG> sees the from as 3:65535/509.1

which PKT format are you sending from your mystic point to MBSE? it must be 
type 2+ or type 2.2 for point and/or domain support...

type 2.2 is the only one that allows for the 5D domain name in the PKT 
header...

type 2+ has certain fields, originzone and destinatiozone, that are duplicated 
but must be set a certain way when a point system is involved... the originnet 
and destinationnet fields are handled differently in this case... you problem 
description appears to show that MBSE is not properly reading the type 2+ PKTs 
from your point system...

easy solution? switch your mystic back to a full node... you can still keep 
your MBSE as a mail hub...

hard solution? fix MBSE's PKT handling code to properly handle Type 2+ PKTs 
from point systems... there is a paper written by one of the Synchronet guys, 
Stephen Hurd, that contains a lot of details about PKTs and how to handle 
them... this information about Type 2+ PKT handling is definitely detailed in 
that paper... i do not recall if the final version was presented to the FTSC 
for publishing, if the FTSC accepted it, or if the FTSC did actually publish 
it... i do recall that someone on the FTSC did make a move to get the paper 
presented to the FTSC but i do not recall that outcome of that, either...


[TIME PASSES]


i was able to go back through my mail archive and find some posts about the 
above document... draft 4 is available at http://bbsdev.net/fsp/FSP-1040.txt 
and i think it is the last draft... the details i speak of above are found in 
the notes portion of the document's section "3. Type 2+ Packet"... the first 
paragraph in that notes section explains why net 65535 is being seen in these 
PKTs and how to properly handle it...


)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it 
wrong...
.... This is your train.  This is your train with Botchmann.  Any questions?
---
 * Origin:  (1:3634/12.73)

.