1. Forum
  2. FidoNet
  3. FIDOSOFT.HUSKY

  • rntrack and full 5D BSO

    From mark lewis@1:3634/12.73 to all on Tue Apr 14 12:49:10 2020

    it rntrack fully 5D complient?

    i have addresses in several FTNs and use 5D BSO so i'm trying to figure out if i need config files for each FTN...

    adding to this confusion is that all the examples and docs show only one FTN address on the Address: line in the configs so i'm not sure if i can specify all my addresses, if they are all to be specified on the one Address: line, or if i have to have multiple Address: lines... additionally, none of the examples
    is using 5D addressing...

    FWIW: my BSO is using the format where all outbounds have the hex extension on them except for my main outbound...

    eg:
    out/fidonet
    out/fidonet.002
    out/vkradio.1b0

    this is due to how my tosser handles 5D BSO and means that i have to lie to binkd and tell it all domains are zone 1...

    )\/(ark

    "The soul of a small kitten in the body of a mighty dragon. Look on my majesty,
    ye mighty, and despair! Or bring me catnip. Your choice. Oooh, a shiny thing!" ... Skydiver's chute didn't open...he jumped to a conclusion.
    ---
    * Origin: (1:3634/12.73)
  • From Michael Dukelsky@2:5020/1042 to mark lewis on Wed Apr 15 19:49:02 2020
    Hello mark,

    Tuesday April 14 2020, mark lewis wrote to all:

    it rntrack fully 5D complient?

    I've never tried using 5D addresses. I looked at the code now and I can say that there are no 5D addresses there.

    i have addresses in several FTNs and use 5D BSO so i'm trying to
    figure out if i need config files for each FTN...

    adding to this confusion is that all the examples and docs show only
    one FTN address on the Address: line in the configs so i'm not sure if
    i can specify all my addresses, if they are all to be specified on the
    one Address: line,

    No, this is not allowed.

    or if i have to have multiple Address: lines...

    This is not allowed either.

    additionally, none of the examples is using 5D addressing...

    Michael

    ... node (at) f1042 (dot) ru
    --- GoldED+/LNX 1.1.5-b20170303
    * Origin: Moscow, Russia (2:5020/1042)
  • From mark lewis@1:3634/12.73 to Michael Dukelsky on Wed Apr 15 13:31:18 2020
    On 2020 Apr 15 19:49:02, you wrote to me:

    it rntrack fully 5D complient?

    I've never tried using 5D addresses. I looked at the code now and I can
    say
    that there are no 5D addresses there.

    ok...

    i have addresses in several FTNs and use 5D BSO so i'm trying to
    figure out if i need config files for each FTN...

    adding to this confusion is that all the examples and docs show only
    one FTN address on the Address: line in the configs so i'm not sure if
    i can specify all my addresses, if they are all to be specified on the
    one Address: line,

    No, this is not allowed.

    or if i have to have multiple Address: lines...

    This is not allowed either.

    well, i guess that settles that... rntrack is not a match for my star hub system with its various addresses and 5D BSO... i'll keep looking... thanks!

    )\/(ark

    "The soul of a small kitten in the body of a mighty dragon. Look on my majesty,
    ye mighty, and despair! Or bring me catnip. Your choice. Oooh, a shiny thing!" ... Transvestites suffer from delusions of gender.
    ---
    * Origin: (1:3634/12.73)