Subj : Re: Possible bug
To   : Rick Smith
From : g00r00
Date : Tue Sep 29 2020 04:34 pm

 RS> Ok I returned the netmail to separate areas ie each network has a set
 RS> node addy in netmail area (it used to work all as one)  Mystic bbs for

There may still be some confusion here.  The instructions I was giving were to
solve the missing address on the origin line.  There was not talk about trying
to create multiple Netmail bases per network (?) so you lost me there! :)

The issue with the missing addressing on the origin line is because those
people have their Netmail base address set as follows:

"Net Address: 0:0/0 (Local Network)"

That is why the addressing was not on the Origin line, because its set local.
I've updated A47 to include the address.

 RS>  gr> I personally host a point system on SCINET, and they are able to send
 RS>  gr> netmails throughout when we tested it.  Netsurge confirmed all of the
 RS>  gr> addressing in the netmails produced from Mystic match the same when
 RS>  gr> they are generated by HPT (the Husky tosser) too.  This was several

 RS> Echo mail works for all networks, only netmail has been affected.  Let
 RS> me know if I can provide any other information...

Yes, I am speaking of Netmail here too.  I believe there are also two FTN
networks that are hubbed entirely by Mystic on a Pi and I haven't heard
anything from them (yet).  It could be unnoticed or that they haven't upgraded
though.

What does the output of "fidopoll route" look like on both the systems you
have?

We weren't able to find an issue with this over SciNet like I said, but we only
tested Windows and Linux not Linux on a Pi (although that really shouldn't
matter).

--- Mystic BBS v1.12 A47 2020/09/27 (Windows/64)
 * Origin: Sector 7 | Mystic WHQ (1:129/215)

.