Subj : MakeNL and how it works?
To : Eric Renfro
From : mark lewis
Date : Sun Sep 06 2015 09:56 am
05 Sep 15 19:04, you wrote to me:
ML>> first off, what version of makenl? hopefully it is the latest ng
ML>> version that is actively being developed and distributed...
ER> MakeNL 3.4.5 custom compiled from an RPM .spec I made to build it and
ER> package it for CentOS 7.1. :) Got that from makenl.sourceforge.net.
ER> Correct, right? ;)
yep!
[trim]
ML>> ==== End "net789.ctl" ====
ER> This is very similar to what I had, with a few lack in some options,
ER> like logging options specifically. :)
i don't remember if they were available in the original or not... redirection
was generally used back then if logging was desired...
ML>> this is basically taken from the bottom half of Figure 2 in the
ML>> original makenl documentation... we're managing all node entries in
ML>> the bottom DATA section and generating a net789.seg file to send
ML>> upstream to the RC... the MSG format netmail directory is where makenl
ML>> will place the file attach message with the seg file for sending... in
ML>> a BSO environment this netmail area needs to be processed by a mail
ML>> tosser to pack the netmail out to the RC's address with the attached
ML>> segment file... if you use an outbound filebox with binkd for your
ML>> connection to your RC, you can throw away the file attach MSG file and
ML>> just copy the net789.ctl file to the outbound filebox directory for
ML>> binkd to send to the RC... this is akin to the way interbbs door game
ML>> files are moved...
ER> Hmmm... When you talk about the outbox, do you mean, the net789.seg could
ER> be directly tossed into the outbox, not the net789.ctl, or do you mean the
ER> literal net789.ctl itself? hehe
if by outbox you mean filebox, then yes, you could place the SEG file in there
directly from makenl but it is better to copy it to the filebox so that makenl
can maintain its own copy... makenl does create and maintain a sequence.dat
file which is queued to the control file's DATA section or to any files brought
in via a FILES section... so the SEG file might not be needed by makenl... i've
not tested that, though...
ER> So long as I'm using BinkD to send these things, I want to use MakeNL
ER> to do what it needs to do, and skip the whole netmail part and toss it
ER> into an outbox just as you say, that is afterall the cleanest way,
ER> instead of having SBBSEcho pack it up and send it.
in your script, just copy the SEG file to the filebox and you should be good to
go...
NOTE: you might want to contact your RC and decide on a name for your netseg
file... this is a security thing... there have been instances in the past where
some neferious person dropped off a false netseg with the same name as a net's
netseg file... the software on the RC's system processed it and replaced the
network section with that of the false netseg... you and your upstream *C just
need to use the same name for your netseg in your scripts so that it will be
processed properly and imposters won't be able to cause problems...
[trim]
ML>> if you want to delve in further, i'm available via netmail...
ER> This is awesome, perfect, and what I was looking for. At least a better
ER> basic understanding. The documentation that comes with it... Isn't very
ER> useful, but explaination of how it's working, like you have provided, was
ER> more helpful.
good deal :)
ER> With the few questions I have left to ask, as such above, and I should
ER> be ready to go.
alright! we're here if needed :)
)\/(ark
... Anything worth taking seriously is worth making fun of.
---
* Origin: (1:3634/12.73)
