• Vmodem Dialing

    From Robert Wolfe@1:261/20 to all on Sat Jul 7 16:14:27 2018
    Hello all!

    Ok, so quick question with using the OS/2 version of FD and SIO/VMODEM like I am using here.

    I would like to be able to set up dialing translations so that any nodes I connect to that have a front end mailer like FrontDoor running on their telnet port can do mailer-to-mailer transfers over telnet.

    My question is where in the FD setup files can I set this up and how is it done?


    --- timEd/2 1.30+
    * Origin: Omicron Theta/2 * Southaven, MS * os2bbs.org:2300 (1:261/20)
  • From mark lewis@1:3634/12.73 to Robert Wolfe on Sat Jul 7 19:50:04 2018

    On 2018 Jul 07 16:14:26, you wrote to all:

    I would like to be able to set up dialing translations so that any
    nodes I connect to that have a front end mailer like FrontDoor running
    on their telnet port can do mailer-to-mailer transfers over telnet.

    do you mean so that your FD will connect to them with telnet or vmodem?

    My question is where in the FD setup files can I set this up and how
    is it done?

    in fdnode.ctl... it is kinda convoluted because of how things were left and because of how the nodelist usage has stalled with the use of IPs or domains in
    the phone field...

    i'll try to describe it quickly...

    1. set up your dial translation table in fdnode.ctl

    DIAL / 011-
    ;internet stuff
    # internet
    0000- internet/:155
    000- internet
    V internet#

    ;local numbers
    blah blah

    2. i use environment variables for the numbers we can connect to in this fashion... in fdnode.ctl, at the top, i have my PHONE entries under my PVTLIST entries

    PHONE 1:261/38 $[janisK]

    3. you can also go ahead and set your COST table...

    COST 15 200
    ;internet translated costs
    # 0
    V 0
    internet 0

    ;local dial costs
    blahblah 5

    4. i have a data file that is used to set these environment variables... my script that runs FD has, at the very top right after the top of the loop, a call to set these environment variables... i use 4DOS/4OS2 which reads a data file and does something with the contents... for my SIO nodes, i have the following...

    for %f in (@%FD\FD_INET.CTL) do set %f

    and FD_INET.CTL looks like this...


    so when the script executes the above line, it set the environment variable janisK which now contains "#filegate.net"...

    i have the same thing for my POTS nodes, too... different CTL file but the same
    variables for all nodes listed in the FD_INET.CTL... this one is named FD_POTS.CTL...


    in this way, both sides of the fence have an environment variable for janis' system... IF a system does not have a POTS number in the nodelist, set its number to "-Unpublished-" OR something like 1-800-555-0100 which is guaranteed in the states to go no where... 555-0100 thru 555-0199 were set up by the telcos for movies to use so that folks didn't go trying to dial numbers they see in movies... that didn't work very well but these numbers still don't go anywhere AFAIK... any area code with 555-0100 works...

    5. so you have your environment variables set up and being refreshed every time
    FD loops to the top of your script... i did it this way so i can edit the FD_INET.CTL or the FD_POTS.CTL to add or change an entry and all i have to do then is to cycle FD out and back through the script OR just wait for it to do it on its own after the next call... make sure these EVs are set and compile your nodelist... the compiler will see that EVs are used for some numbers and FD will look for them in the environment when it tries to load information for that node... in this example, after you compile the nodelist, use the nodelist browser and go look at janis' 1:261/38 entry... it should have either $[janisK]
    OR "#filegate.net" entry OR the phone number or "-Unpublished-" if you put that
    in, depending on which node you are looking with... that's important... if you are looking at that entry with a SIO node, it should have the filegate.net entry... if you're looking from a POTS node, it should have whatever you put in
    for the phone number in the FD_POTS.ctl file...

    6. lastly, in fdsetup->manager->modem, we set up something for the nodelist flags...

    ITN: (Do not dial)
    IVN: (Do not dial)
    ITN (stop scanning, proceed with call)

    i also have specific entries for each of the nodes that i connect to via telnet
    or vmodem... they're in the same place and look like this...

    1:261/38 (stop scanning, proceed with call)

    and at the very bottom of the list, this entry has to be last, IIRC...

    >0 (Do not dial)

    so, a nodelist entry with a ITN or IVM flag gets dialed... we cannot dial those
    with the colon because FD cannot read that from the nodelist... and since we're
    doing this with environment variables, we can just add the port to the FD_INET.CTL file if it is needed... it is listed after the domain or IP number like so...

    janisK=#filegate.net 2323

    i've done this from memory as i have to go in a minute but i wanted to get this
    out while i was thinking about it... you don't have to use my file names or environment variables... i tried using the node numbers, eg: 1-261-38 or even doing them with the color and slash but had problems that i don't recall... my method definitely requires 4DOS/4OS2... if you don't have that, you can just list all the set commands in your script that runs FD... just remember that you
    cannot edit them while the script is running (ie: when FD is loaded)...

    i never got around to writing anything to pull this information from the nodelist and put it in my CTL files... way back there were a lot more nodes with telnet or vmodem capability... these days, not so much... i only ever made
    entries for those systems that i actually connected to... i didn't ever try to make it so i could connect to any system... it just wasn't worth the trouble when using this method...

    i'm sure i've left something out... if you find it or have problems, just ask... i gotta go, i'm running behind now... have fun!


    Always Mount a Scratch Monkey
    Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
    ... Never enough time, unless you're serving it.
    * Origin: (1:3634/12.73)