• defnode

    From Alan Ianson@1:153/757 to All on Wed Aug 17 17:38:00 2016
    Hello All,

    I am trying to add "defnode *" to my binkd.conf so I can send netmail directly to nodes I don't have a node line in my binkd.conf. When I do that binkd uses the wrong domain and fails for nodes I do have listed, as below..

    ==== Begin "binkd.txt" ====
    + 17 Aug 17:32:03 [8179] call to 1:153/7715@agoranet
    17 Aug 17:32:03 [8179] trying 70.79.72.72...
    17 Aug 17:32:03 [8179] connected
    + 17 Aug 17:32:03 [8179] outgoing session with S01061c1b689f0ca3.vc.shawcable.net [70.79.72.72] (24554)
    - 17 Aug 17:32:23 [8179] OPT MB CRAM-MD5-42467e500cbf5fa7c34c6dde6205ec9e
    + 17 Aug 17:32:23 [8179] Remote requests MD mode
    - 17 Aug 17:32:23 [8179] SYS BandMaster BBS
    - 17 Aug 17:32:23 [8179] ZYZ Dallas Hinton
    - 17 Aug 17:32:23 [8179] LOC The BandMaster, Vancouver, BC, Canada
    - 17 Aug 17:32:23 [8179] NDL IBN
    - 17 Aug 17:32:23 [8179] TIME 2016/08/17 17:32:19 -8:00
    - 17 Aug 17:32:23 [8179] VER Internet Rex 2.29 Win32 (binkp/1.1)
    + 17 Aug 17:32:23 [8179] addr: 1:153/7715@fidonet
    + 17 Aug 17:32:23 [8179] addr: 1:153/715@fidonet
    + 17 Aug 17:32:23 [8179] addr: 1:153/716@fidonet
    + 17 Aug 17:32:23 [8179] addr: 1:10295/0@fidonet
    + 17 Aug 17:32:23 [8179] addr: 1:153/0@fidonet
    ? 17 Aug 17:32:23 [8179] called 1:153/7715@agoranet, but remote has no such AKA + 17 Aug 17:32:23 [8179] holding 1:153/7715@agoranet (2016/08/17 18:32:23)
    + 17 Aug 17:32:23 [8179] done (to 1:153/7715@agoranet, failed, S/R: 0/0 (0/0 bytes))
    17 Aug 17:32:23 [8179] session closed, quitting...
    ==== End "binkd.txt" ====

    Why is binkd polling 1:153/7715@agoranet? Agoranet is one of the domains I have
    in my setup for zone 46, but that poll you be for 1:153/7715@fidonet.

    This only happens when I add "defnode *" to my binkd.conf, if I leave it commented out all is working as expected.

    What have I done wrong?

    Ttyl :-),
    Al

    ... Always look out for #1 and be careful not to step in #2.
    --- GoldED+/LNX 1.1.5-b20160322
    * Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)
  • From Allen Prunty@1:2320/100 to Alan Ianson on Thu Aug 18 06:39:16 2016

    On Aug 17, 2016 05:45pm, Alan Ianson wrote to All:

    Hello All,

    I am trying to add "defnode *" to my binkd.conf so I can send netmail directly to nodes I don't have a node line in my binkd.conf. When I do that binkd uses the wrong domain and fails for nodes I do have listed,
    as below..

    I have figured out that if you use defnode * and it references binkp.net the node you are trying to connect with has to be listed at http://binkp.net

    They have done what they can to pick up the nodelist but when I checked 1:2320/100 was listed as derbycitybbs.com which was the domain I used in 2012.

    I recreated my node and got a crash mail... opened the link and BOOM it has me set up right now. It also tracks my ip address and all I have to do is poll their FTN node.

    I think the only nodes listed there are zone 1-4 though.

    This only happens when I add "defnode *" to my binkd.conf, if I leave it commented out all is working as expected.

    What have I done wrong?

    I don't think you have done ANYTHING wrong... the node needs to update at binkp.net

    Allen

    ... The greatest enemy of creatitivy is staying inside your comfort zone
    --- Platinum Xpress/Win/WINServer v3.0pr5
    * Origin: LiveWire -=* Louisville, KY USA *=- LiveWireBBS.Com (1:2320/100)
  • From Alan Ianson@1:153/757 to Allen Prunty on Thu Aug 18 14:40:00 2016
    Thursday August 18 2016 06:39, you wrote to me:

    This only happens when I add "defnode *" to my binkd.conf, if I
    leave it commented out all is working as expected.

    What have I done wrong?

    I don't think you have done ANYTHING wrong... the node needs to update
    at binkp.net

    I've got something wrong here that only shows itself when I add "defnode *" to my binkd.conf. Instead of polling 1:2320/100@fidonet (for example) it tries to poll 1:2320/100@agoranet and that fails because that node doesn't have such an aka. It does the same for the other zones I have here also.

    binkp.net does work here as expected.

    Ttyl :-),
    Al

    ... My spelling? Oh, it's just line noise.
    --- GoldED+/LNX 1.1.5-b20160322
    * Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)
  • From Kees van Eeten@2:280/5003.4 to Alan Ianson on Thu Aug 18 23:58:10 2016
    Hello Alan!

    18 Aug 16 14:40, you wrote to Allen Prunty:

    This only happens when I add "defnode *" to my binkd.conf, if I
    leave it commented out all is working as expected.

    What have I done wrong?

    I don't think you have done ANYTHING wrong... the node needs to update
    at binkp.net

    I've got something wrong here that only shows itself when I add "defnode *" to my binkd.conf. Instead of polling 1:2320/100@fidonet (for example) it tries to poll 1:2320/100@agoranet and that fails because that node doesn't have such an aka. It does the same for the other zones I have here also.

    binkp.net does work here as expected.

    You will have to reajust your expectations.

    The following line should be in your config file.

    -------------------------------
    #
    # Overrides root domain for DNS lookups, see `node' below.
    #
    root-domain binkp.net
    -----------------

    That forces de domain for defnode and "*" notations for hostnames.

    The "*" notation forces binkd to use the following hostname

    fn.nx.zy.binkd.net

    Where x=nodenumber, y=netnumber, z=zonenumber

    Kees

    --- GoldED+/LNX 1.1.5
    * Origin: As for me, all I know is that, I know nothing. (2:280/5003.4)
  • From Kees van Eeten@2:280/5003.4 to Kees van Eeten on Fri Aug 19 00:10:58 2016
    Hello!

    Please note that it should be fn.nx.zy.binkp.net

    As far as I know the DNS service at binkp.net is updated from the
    DAILYLST as published in Z2. Additionally entries are added from their
    dynamic DNS service.



    18 Aug 16 23:58, I wrote to Alan Ianson:

    Hello Alan!

    18 Aug 16 14:40, you wrote to Allen Prunty:

    This only happens when I add "defnode *" to my binkd.conf, if I
    leave it commented out all is working as expected.

    What have I done wrong?

    I don't think you have done ANYTHING wrong... the node needs to
    update at binkp.net

    I've got something wrong here that only shows itself when I add
    "defnode *" to my binkd.conf. Instead of polling 1:2320/100@fidonet
    (for example) it tries to poll 1:2320/100@agoranet and that fails
    because that node doesn't have such an aka. It does the same for the
    other zones I have here also.

    binkp.net does work here as expected.

    You will have to reajust your expectations.

    The following line should be in your config file.

    -------------------------------
    #
    # Overrides root domain for DNS lookups, see `node' below.
    #
    root-domain binkp.net
    -----------------

    That forces de domain for defnode and "*" notations for hostnames.

    The "*" notation forces binkd to use the following hostname

    fn.nx.zy.binkd.net

    Where x=nodenumber, y=netnumber, z=zonenumber

    Kees

    --- GoldED+/LNX 1.1.5
    * Origin: As for me, all I know is that, I know nothing. (2:280/5003.4)

    Kees

    --- GoldED+/LNX 1.1.5
    * Origin: As for me, all I know is that, I know nothing. (2:280/5003.4)
  • From Alan Ianson@1:153/757 to Kees van Eeten on Thu Aug 18 16:20:00 2016
    Thursday August 18 2016 23:58, you wrote to me:

    I've got something wrong here that only shows itself when I add
    "defnode *" to my binkd.conf. Instead of polling
    1:2320/100@fidonet (for example) it tries to poll
    1:2320/100@agoranet and that fails because that node doesn't have
    such an aka. It does the same for the other zones I have here
    also.

    binkp.net does work here as expected.

    You will have to reajust your expectations.

    I need to adjust something I think but I am not sure what.

    The following line should be in your config file.

    -------------------------------
    #
    # Overrides root domain for DNS lookups, see `node' below.
    #
    root-domain binkp.net
    -----------------

    That is there and does work, as long as I leave "defnode *" commented out in my
    binkd.conf.

    I just polled your node twice. The first time I had "defnode *" uncommented in my binkd.conf. This is what the log says.


    ==== Begin "binkd1.log" ====

    18 Aug 16:16:26 [31700] BEGIN, binkd/1.0.5-pre5/Linux -pP2:280/5003 /usr/local/etc/binkd.conf
    ? 18 Aug 16:16:26 [31700] Cannot find domain for zone 2, assuming 'fidonet'
    18 Aug 16:16:26 [31700] creating a poll for 2:280/5003@fidonet (`d' flavour)
    18 Aug 16:16:26 [31700] clientmgr started
    18 Aug 16:16:27 [31700] 2:280/5003@dorenet busy, skipping
    + 18 Aug 16:16:27 [31701] call to 2:280/5003@agoranet
    18 Aug 16:16:27 [31700] 2:280/5003@fidonet busy, skipping
    18 Aug 16:16:27 [31702] 2:280/5003@cybernet busy, skipping
    18 Aug 16:16:27 [31700] 2:280/5003@fsxnet busy, skipping
    18 Aug 16:16:27 [31700] 2:280/5003@ilink busy, skipping
    18 Aug 16:16:27 [31700] 2:280/5003@micronet busy, skipping
    18 Aug 16:16:27 [31700] 2:280/5003@sportnet busy, skipping
    18 Aug 16:16:27 [31700] 2:280/5003@survnet busy, skipping
    18 Aug 16:16:27 [31700] 2:280/5003@wwivftn busy, skipping
    18 Aug 16:16:27 [31700] rc(31702)=0
    18 Aug 16:16:27 [31701] trying 84.106.181.21...
    18 Aug 16:16:27 [31701] connected
    + 18 Aug 16:16:27 [31701] outgoing session with 546AB515.cm-12-3c.dynamic.ziggo.nl [84.106.181.21] (24554)
    - 18 Aug 16:16:29 [31701] OPT CRAM-MD5-756aa597533738bfc2f0141f75d52bee
    + 18 Aug 16:16:29 [31701] Remote requests MD mode
    - 18 Aug 16:16:29 [31701] SYS Double Dutch
    - 18 Aug 16:16:29 [31701] ZYZ Kees Van Eeten
    - 18 Aug 16:16:29 [31701] LOC Heerhugowaard, The Netherlands
    - 18 Aug 16:16:29 [31701] NDL 115200,TCP,BINKP
    - 18 Aug 16:16:29 [31701] TIME Fri, 19 Aug 2016 01:16:29 +0200
    - 18 Aug 16:16:29 [31701] VER binkd/1.1a-94/Linux binkp/1.1
    + 18 Aug 16:16:36 [31701] addr: 2:280/5003@fidonet
    + 18 Aug 16:16:37 [31701] addr: 2:280/0@fidonet
    ? 18 Aug 16:16:37 [31701] called 2:280/5003@agoranet, but remote has no such AKA
    + 18 Aug 16:16:37 [31701] done (to 2:280/5003@agoranet, failed, S/R: 0/0 (0/0 bytes))
    18 Aug 16:16:37 [31701] session closed, quitting...
    18 Aug 16:16:37 [31700] rc(31701)=0
    18 Aug 16:16:37 [31700] the queue is empty, quitting...
    ==== End "binkd1.log" ====

    That failed so I commented "defnode *" in my binkd.conf and tried again with the same command line. The log looks like this..


    ==== Begin "binkd2.log" ====

    18 Aug 16:17:15 [31718] BEGIN, binkd/1.0.5-pre5/Linux -pP2:280/5003 /usr/local/etc/binkd.conf
    ? 18 Aug 16:17:15 [31718] Cannot find domain for zone 2, assuming 'fidonet'
    18 Aug 16:17:15 [31718] creating a poll for 2:280/5003@fidonet (`d' flavour)
    18 Aug 16:17:15 [31718] clientmgr started
    + 18 Aug 16:17:15 [31719] call to 2:280/5003@fidonet
    18 Aug 16:17:15 [31719] trying 84.106.181.21...
    18 Aug 16:17:15 [31719] connected
    + 18 Aug 16:17:15 [31719] outgoing session with 546AB515.cm-12-3c.dynamic.ziggo.nl [84.106.181.21] (24554)
    - 18 Aug 16:17:15 [31719] OPT CRAM-MD5-0f9bb021865a1fcc86f63d4927d643ee
    + 18 Aug 16:17:15 [31719] Remote requests MD mode
    - 18 Aug 16:17:15 [31719] SYS Double Dutch
    - 18 Aug 16:17:15 [31719] ZYZ Kees Van Eeten
    - 18 Aug 16:17:15 [31719] LOC Heerhugowaard, The Netherlands
    - 18 Aug 16:17:15 [31719] NDL 115200,TCP,BINKP
    - 18 Aug 16:17:15 [31719] TIME Fri, 19 Aug 2016 01:17:15 +0200
    - 18 Aug 16:17:15 [31719] VER binkd/1.1a-94/Linux binkp/1.1
    + 18 Aug 16:17:15 [31719] addr: 2:280/5003@fidonet
    + 18 Aug 16:17:15 [31719] addr: 2:280/0@fidonet
    - 18 Aug 16:17:16 [31719] OPT EXTCMD GZ BZ2
    + 18 Aug 16:17:16 [31719] Remote supports EXTCMD mode
    + 18 Aug 16:17:16 [31719] Remote supports GZ mode
    + 18 Aug 16:17:16 [31719] Remote supports BZ2 mode
    + 18 Aug 16:17:16 [31719] done (to 2:280/5003@fidonet, OK, S/R: 0/0 (0/0 bytes))
    18 Aug 16:17:16 [31719] session closed, quitting...
    18 Aug 16:17:16 [31718] rc(31719)=0
    18 Aug 16:17:16 [31718] the queue is empty, quitting...
    ==== End "binkd2.log" ====

    That one looks good. I was hoping to add "defnode *" to my config so binkd would deliver direct or crash mail to a node not in my binkd.conf directly.

    I also wonder about the not being able to find domain for zone 2 line at the top of the log. I wonder if that is normal.

    Ttyl :-),
    Al

    ... Internal error: The sytem has been taken over by sheep at line 19960
    --- GoldED+/LNX 1.1.5-b20160322
    * Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)
  • From Allen Prunty@1:2320/100 to Alan Ianson on Thu Aug 18 22:25:12 2016

    On Aug 18, 2016 02:47pm, Alan Ianson wrote to Allen Prunty:

    Thursday August 18 2016 06:39, you wrote to me:

    This only happens when I add "defnode *" to my binkd.conf, if I
    leave it commented out all is working as expected.

    What have I done wrong?

    I don't think you have done ANYTHING wrong... the node needs to update
    at binkp.net

    I've got something wrong here that only shows itself when I add
    "defnode *" to my binkd.conf. Instead of polling 1:2320/100@fidonet
    (for example) it tries to poll 1:2320/100@agoranet and that fails
    because that node doesn't have such an aka. It does the same for the
    other zones I have here also.

    binkp.net does work here as expected.

    That's whacked as I don't use agoranet.

    I put 5D entries in all of my node entries like so...

    node 21:1/100.0@fsxnet -6 ipv6.agency.bbs.geek.nz:24556;* NUNYA i c:\\pxw\ \fsxnet\\out

    In this case it's no question it's fxnet

    Was told everything works better when the node is completely speced out.

    In your case it shouild start with...

    node 1:2320/100.0@fidonet ....

    This way BinkD knows my domain is fidonet and it doesn't have to guess

    Allen

    ... The greatest enemy of creatitivy is staying inside your comfort zone
    --- Platinum Xpress/Win/WINServer v3.0pr5
    * Origin: LiveWire -=* Louisville, KY USA *=- LiveWireBBS.Com (1:2320/100)
  • From Allen Prunty@1:2320/100 to Kees van Eeten on Thu Aug 18 22:27:24 2016

    On Aug 18, 2016 11:56pm, Kees van Eeten wrote to Alan Ianson:


    binkp.net does work here as expected.

    You will have to reajust your expectations.

    The following line should be in your config file.

    -------------------------------
    #
    # Overrides root domain for DNS lookups, see `node' below.
    #
    root-domain binkp.net
    -----------------

    That forces de domain for defnode and "*" notations for hostnames.

    The "*" notation forces binkd to use the following hostname

    fn.nx.zy.binkd.net

    Where x=nodenumber, y=netnumber, z=zonenumber


    I have that in my config... everything works perfecto.

    I also verified my entry with binkp.net very simple but it took a while for
    the verification to get crashed to me.

    Allen

    ... The greatest enemy of creatitivy is staying inside your comfort zone
    --- Platinum Xpress/Win/WINServer v3.0pr5
    * Origin: LiveWire -=* Louisville, KY USA *=- LiveWireBBS.Com (1:2320/100)
  • From Alan Ianson@1:153/757 to Allen Prunty on Thu Aug 18 20:24:00 2016
    Thursday August 18 2016 22:25, you wrote to me:

    [...]

    That's whacked as I don't use agoranet.

    I put 5D entries in all of my node entries like so...

    node 21:1/100.0@fsxnet -6 ipv6.agency.bbs.geek.nz:24556;* NUNYA i c:\\pxw\ \fsxnet\\out

    In this case it's no question it's fxnet

    Was told everything works better when the node is completely speced
    out.

    In your case it shouild start with...

    node 1:2320/100.0@fidonet ....

    This way BinkD knows my domain is fidonet and it doesn't have to guess

    Allen

    ... The greatest enemy of creatitivy is staying inside your comfort
    zone
    --- Platinum Xpress/Win/WINServer v3.0pr5
    * Origin: LiveWire -=* Louisville, KY USA *=- LiveWireBBS.Com (1:2320/100)

    Well, yes. But do you have anything to say regarding the question I posted?

    Ttyl :-),
    Al

    ... You can name your salary here, I call mine fred.
    --- GoldED+/LNX 1.1.5-b20160322
    * Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)
  • From mark lewis@1:3634/12.73 to Allen Prunty on Fri Aug 19 15:29:36 2016

    18 Aug 16 06:39, you wrote to Alan Ianson:

    I think the only nodes listed there are zone 1-4 though.

    becaues binkp.net is only for fidonet addresses... othernets need to have their
    own DNS lookup services for the f.n.z conversion format...

    eg:
    1:3634/12 == n12.f3634.z1.binkp.net (for fidonet)
    46:1/75 == n75.f1.z46.agora.net (for agoranet)

    the above are just examples but the binkp.net one is accurate as binkp.net was set up to provide this service for fidonet since fidonet.net (or .org or whatever it was) was lost to a domain squatter who wants like $10000 for the domain... one ouwld have to check with agoranet to see if the have a DNS service for their members' nodes and if they do, what DNS domain to use for those DNS lookups...

    )\/(ark

    Always Mount a Scratch Monkey

    ... New oxymoron: final beta
    ---
    * Origin: (1:3634/12.73)
  • From mark lewis@1:3634/12.73 to Kees van Eeten on Fri Aug 19 15:20:14 2016

    18 Aug 16 23:58, you wrote to Alan Ianson:

    I've got something wrong here that only shows itself when I add
    "defnode *" to my binkd.conf. Instead of polling 1:2320/100@fidonet
    (for example) it tries to poll 1:2320/100@agoranet and that fails
    because that node doesn't have such an aka. It does the same for the
    other zones I have here also.

    binkp.net does work here as expected.

    You will have to reajust your expectations.

    agreed...

    The following line should be in your config file.

    -------------------------------
    #
    # Overrides root domain for DNS lookups, see `node' below.
    #
    root-domain binkp.net
    -----------------

    this is *best* done with the new format... especially for those in multiple FTN
    networks... the new format is

    domain fidonet /ftn/outbound/fidonet 1 binkp.net
    domain foobarz /ftn/outbound/foobarz 1234 foobarz.net
    domain barfood /ftn/outbound/barfood 321 barfood.org

    where binkp.net, foobarz.net and barfood.org are the domains to use for the f.n.z conversion DNS lookups... and leave out the "root-domain" line completely...

    NOTE1: the above examples are for 5D BSO... use the proper directory format for
    your BSO directories and just add the DNS lookup domain on the end... othernets
    that actually have a f.n.z DNS lookup service will be able to tell their members what domain to use for their f.n.z DNS lookups...

    NOTE2: in the above example, binkp.net is the only valid and actually existing service... the others are pure examples...

    )\/(ark

    Always Mount a Scratch Monkey

    ... Some people are just for looks.
    ---
    * Origin: (1:3634/12.73)
  • From Tony Langdon@3:633/410 to mark lewis on Sat Aug 20 08:08:00 2016
    mark lewis wrote to Kees van Eeten <=-


    this is *best* done with the new format... especially for those in multiple FTN networks... the new format is

    domain fidonet /ftn/outbound/fidonet 1 binkp.net
    domain foobarz /ftn/outbound/foobarz 1234 foobarz.net
    domain barfood /ftn/outbound/barfood 321 barfood.org

    What version of binkd do you need to be able to use this format? It's certainly much better, as I had issues with using the root-domain configuration, with my othernets. I'd have kept using binkp.net, if I could restrict its use to Fidonet addresses. It plays havoc with othernets, so the above per domain format makes more sense.


    ... Dime:... A dollar with all the taxes taken out.
    --- MultiMail/Win32 v0.49
    * Origin: Freeway BBS - freeway.apana.org.au (3:633/410)
  • From Richard Menedetter@2:310/31 to Alan Ianson on Sat Aug 20 01:54:06 2016
    Hi Alan!

    17 Aug 2016 17:38, from Alan Ianson -> All:

    I am trying to add "defnode *" to my binkd.conf so I can send netmail directly to nodes I don't have a node line in my binkd.conf. When I do that binkd uses the wrong domain and fails for nodes I do have listed,
    as below..

    I had the same issue.
    I have forgotten the details (I think it has to do with the DNS lookup [binkp.net] and assuming that it can use it for the wrong fido domain)

    Anyways ... my solution looks like this:

    #defnode *
    include /usr/local/etc/binkd.inc

    I have a script that converts the fidonet daily nodelist to a binkd include file.

    CU, Ricsi

    --- GoldED+/LNX
    * Origin: Smuggling is just commodity relocation. (2:310/31)
  • From Allen Prunty@1:2320/100 to Richard Menedetter on Fri Aug 19 22:04:36 2016

    On Aug 20, 2016 01:52am, Richard Menedetter wrote to Alan Ianson:
    Hey Ricksi...

    Anyways ... my solution looks like this:

    #defnode *
    include /usr/local/etc/binkd.inc

    I have a script that converts the fidonet daily nodelist to a binkd include file.

    You have been quiet too long starting to wonder if you are ok. Would you consider sharing the script? Another person who seems to be gifted with
    python scrips is Wilfred who has written a simple script to insert a .pkt password in a netmail .pkt that doesn't have one.

    Allen

    ... The greatest enemy of creatitivy is staying inside your comfort zone
    --- Platinum Xpress/Win/WINServer v3.0pr5
    * Origin: LiveWire -=* Louisville, KY USA *=- LiveWireBBS.Com (1:2320/100)
  • From Richard Menedetter@2:310/31 to Allen Prunty on Sat Aug 20 10:39:34 2016
    Hi Allen!

    19 Aug 2016 22:04, from Allen Prunty -> Richard Menedetter:

    I have a script that converts the fidonet daily nodelist to a
    binkd include file.
    You have been quiet too long starting to wonder if you are ok.

    Was away for 2 weeks, and the fido node crashed (?) after 2 days ...
    Came back thought it was a dead storage, rebooted, and it works again.

    Would you consider sharing the script?

    I only use that script, it was not written by me.

    # nl2binkd v1.07
    # (c) 2012-2016 by Markus Reschke
    # Fidonet 2:240/1661 / madires@theca-tabellaria.de

    Works very well, and evades the issues with defnode * and othernets, while still being able to crash every fido node with binkp.

    CU, Ricsi

    --- GoldED+/LNX
    * Origin: After we pull the pin, Mr. Grenade is NOT our friend! (2:310/31)
  • From mark lewis@1:3634/12.73 to Tony Langdon on Sat Aug 20 04:08:16 2016

    20 Aug 16 08:08, you wrote to me:

    this is *best* done with the new format... especially for those in
    multiple FTN networks... the new format is

    domain fidonet /ftn/outbound/fidonet 1 binkp.net
    domain foobarz /ftn/outbound/foobarz 1234 foobarz.net
    domain barfood /ftn/outbound/barfood 321 barfood.org

    What version of binkd do you need to be able to use this format?

    TBH, i'm not sure... i pointed out the problem with using root-domain and being
    in multiple FTN othernets and binkp.net doing only fidonet addresses some time back... one of the developers told me about this format but it has been several
    years ago... i don't recall their name but i think it was stas degteff as he helped me with other aspects of a full 5D configuration and what the outbound directory tree would look like... this alternative method of listing DNS lookup
    domains is not specific to 5D, though... on my main machine, i have locked several messages in my message base to keep them from being purged... those discussions were back in 2012 but apparently i failed to lock the ones concerning this format of the domain lines and i don't see anything in the FAQ about it :(

    It's certainly much better, as I had issues with using the root-domain configuration, with my othernets. I'd have kept using binkp.net, if I could restrict its use to Fidonet addresses. It plays havoc with othernets, so the above per domain format makes more sense.

    it absolutely does make more sense... the real trick is to get othernets to set
    up their own DNS lookup domain zones...

    )\/(ark

    Always Mount a Scratch Monkey

    ... Hot sauces are final products having recipes, not ingredients.
    ---
    * Origin: (1:3634/12.73)
  • From Allen Prunty@1:2320/100 to Richard Menedetter on Sat Aug 20 06:11:56 2016
    Hi Allen!

    Was away for 2 weeks, and the fido node crashed (?) after 2 days ...
    Came back thought it was a dead storage, rebooted, and it works again.

    It must have been exhausted... it needed rest. Glad you are back.

    Would you consider sharing the script?

    I only use that script, it was not written by me.

    # nl2binkd v1.07
    # (c) 2012-2016 by Markus Reschke
    # Fidonet 2:240/1661 / madires@theca-tabellaria.de

    Works very well, and evades the issues with defnode * and othernets, while still being able to crash every fido node with binkp.

    You will be proud of me I have bink-d working now, and it is connectable
    via ipv6 at ipv6.livewirebbs.com guess I'm only sligltly less brain
    damaged than I thought I was.

    Allen

    --- Platinum Xpress/Win/WINServer v3.0pr5
    * Origin: LiveWire -=* Louisville, KY USA *=- LiveWireBBS.Com (1:2320/100)
  • From Richard Menedetter@2:310/31 to Allen Prunty on Sat Aug 20 13:49:38 2016
    Hi Allen!

    20 Aug 2016 06:11, from Allen Prunty -> Richard Menedetter:

    Was away for 2 weeks, and the fido node crashed (?) after 2 days
    ... -> Came back thought it was a dead storage, rebooted, and it works again.
    It must have been exhausted... it needed rest.

    Indeed ;)
    I was happy that it was so easy to revive.

    You will be proud of me I have bink-d working now, and it is
    connectable via ipv6 at ipv6.livewirebbs.com

    Yes ... works.

    Some comments:
    The hosts differs from the one in the nodelist.
    You can add A and AAAA records, and the IPv6 capable nodes will automatically connect via IPv6 and the rest with IPv4.

    Also it seems you do not have the password that I have sent you in the config -
    I get an unsecured connection.

    fido@odroid:~$ poll 1:2320/100
    + 13:49 [16893] call to 1:2320/100@fidonet
    13:49 [16893] trying ipv6.livewirebbs.com [2602:306:83c1:a710::48]...
    ? 13:49 [16893] Warning: remote set UNSECURE session
    + 13:49 [16893] pwd protected session (MD5)

    CU, Ricsi

    --- GoldED+/LNX
    * Origin: Only the stupidest calves chose their own butcher (2:310/31)
  • From Allen Prunty@1:2320/100 to Richard Menedetter on Sat Aug 20 08:02:34 2016

    On Aug 20, 2016 01:47pm, Richard Menedetter wrote to Allen Prunty:

    Hi Allen!

    20 Aug 2016 06:11, from Allen Prunty -> Richard Menedetter:

    Some comments:
    The hosts differs from the one in the nodelist.
    You can add A and AAAA records, and the IPv6 capable nodes will automatically connect via IPv6 and the rest with IPv4.

    Unfortunately for me my provider does not give me that option. I have to
    split them for the time being. Since there are more ipv4's now... have to
    keep that in the nodelist. I may list 2320/0 as the ipv6 node.

    Also it seems you do not have the password that I have sent you in the config - I get an unsecured connection.

    I'm sorry but in a system crash I lost your password... you can e-mail it to
    me at allen.prunty@livewirebbs.com and I'll get it.

    Now that I'm on genuine Bink-D I should be more confident that my connections will get through here ok.

    Allen

    ... The greatest enemy of creatitivy is staying inside your comfort zone
    --- Platinum Xpress/Win/WINServer v3.0pr5
    * Origin: LiveWire -=* Louisville, KY USA *=- LiveWireBBS.Com (1:2320/100)
  • From Tony Langdon@3:633/410 to mark lewis on Sat Aug 20 21:21:00 2016
    mark lewis wrote to Tony Langdon <=-

    What version of binkd do you need to be able to use this format?

    TBH, i'm not sure... i pointed out the problem with using root-domain
    and being in multiple FTN othernets and binkp.net doing only fidonet addresses some time back... one of the developers told me about this format but it has been several years ago... i don't recall their name
    but i think it was stas degteff as he helped me with other aspects of a full 5D configuration and what the outbound directory tree would look like... this alternative method of listing DNS lookup domains is not specific to 5D, though... on my main machine, i have locked several messages in my message base to keep them from being purged... those discussions were back in 2012 but apparently i failed to lock the ones concerning this format of the domain lines and i don't see anything in
    the FAQ about it :(

    Yes, I never knew about this format until you mentioned it here. Keen to know more. It's not in any of my examples.

    it absolutely does make more sense... the real trick is to get
    othernets to set up their own DNS lookup domain zones...

    What's involved in setting the lookup service up? I can register and administer domains (have done for years, though in this case, it would be a subdomain of an existing domain), and I recently started an othernet, so I would be interested in what I'd need to do to setup the service for my net.


    ... Features should be discovered, not documented.
    --- MultiMail/Win32 v0.49
    * Origin: Freeway BBS - freeway.apana.org.au (3:633/410)
  • From mark lewis@1:3634/12.73 to Tony Langdon on Sat Aug 20 11:12:36 2016

    20 Aug 16 21:21, you wrote to me:

    those discussions were back in 2012 but apparently i failed to lock
    the ones concerning this format of the domain lines and i don't see
    anything in the FAQ about it :(

    Yes, I never knew about this format until you mentioned it here. Keen
    to know more. It's not in any of my examples.

    it absolutely does make more sense... the real trick is to get
    othernets to set up their own DNS lookup domain zones...

    What's involved in setting the lookup service up?

    basically it is two parts...

    1. have a script to convert the nodelist into a/some DNS zone files
    for whatever DNS host server software is being used.

    2. set up a DNS host server to use the zone files created in step 1
    and allow public access to that DNS server so anyone in the
    world can look up fzzz.nyyy.zxxx.your.domain.


    I can register and administer domains (have done for years, though in
    this case, it would be a subdomain of an existing domain), and I
    recently started an othernet, so I would be interested in what I'd
    need to do to setup the service for my net.

    the folks running binkp.net would have more information than the little i have... i know the concepts and have run my own stuff in the distant past but don't remember all the details... the main thing is that the addresses in the nodelist are converted to the f.n.z format in the zone file that the DNS server
    presents to the world when queries are made of it... some DNS servers use a simple HOSTS file type of format... others are akin to what bind uses...

    so basically, you have the overall othernet domain with at least one zone sub-domain (zxxx) with at least one net sub-domain (nyyy) and each FTN node in that FTN net has a host entry in that net's sub-domain (fzzz)... a lookup for fzzz.nyyy.zxxx.othernet.domain will return either the IP number from the nodelist or a CNAME if the nodelist contains host.domain.name for that node...

    in these examples, 'xxx' is the zone number, 'yyy' is the net number and 'zzz' is the node number... the 'f', 'n' and 'z' are important...

    eg: f99.n276.z486.some.othernet == 486:276/99

    point addresses would have a 'p' leading them if you publish points in your zone file... otherwise, a wildcard will also be needed for each node so that any connection attempts to deliver point mail are sent to the node hosting the points...

    i think i've covered most all of it... does it make sense to you??

    )\/(ark

    Always Mount a Scratch Monkey

    ... "God Jul och Gott Nytt aar." - Swedish Christmas
    ---
    * Origin: (1:3634/12.73)
  • From Alan Ianson@1:153/757 to Richard Menedetter on Sat Aug 20 13:56:00 2016
    Saturday August 20 2016 01:54, you wrote to me:

    Anyways ... my solution looks like this:

    #defnode *
    include /usr/local/etc/binkd.inc

    Thanks Richard, that'll work for me I think.. :)

    Ttyl :-),
    Al

    ... Baroque: When you are out of Monet.
    --- GoldED+/LNX 1.1.5-b20160322
    * Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)
  • From Tony Langdon@3:633/410 to mark lewis on Sun Aug 21 08:18:00 2016
    mark lewis wrote to Tony Langdon <=-

    What's involved in setting the lookup service up?

    basically it is two parts...

    1. have a script to convert the nodelist into a/some DNS zone files
    for whatever DNS host server software is being used.

    2. set up a DNS host server to use the zone files created in step 1
    and allow public access to that DNS server so anyone in the
    world can look up fzzz.nyyy.zxxx.your.domain.

    Yep, that makes sense to me.

    i think i've covered most all of it... does it make sense to you??

    The concept makes perfect sense. The main question would be how to implement it. The guys gtom binkp.net would be helpful for the details of implementation. :)


    ... The difference between haste and waste are the leading letters.
    --- MultiMail/Win32 v0.49
    * Origin: Freeway BBS - freeway.apana.org.au (3:633/410)
  • From Paul Hayton@3:770/100 to mark lewis on Mon Aug 22 22:32:32 2016
    On 08/20/16, mark lewis pondered and said...

    1. have a script to convert the nodelist into a/some DNS zone files
    for whatever DNS host server software is being used.

    2. set up a DNS host server to use the zone files created in step 1
    and allow public access to that DNS server so anyone in the
    world can look up fzzz.nyyy.zxxx.your.domain.


    Thanks Mark for the info..

    This is something I have little experience in, but I too am interested in setting something like this up. Tony, do you want to work together on this?

    Best, Paul

    --- Mystic BBS v1.12 A31 (Windows)
    * Origin: Agency BBS | telnet://agency.bbs.geek.nz (3:770/100)
  • From Tony Langdon@3:633/410 to Paul Hayton on Tue Aug 23 20:06:00 2016
    Paul Hayton wrote to mark lewis <=-

    Thanks Mark for the info..

    This is something I have little experience in, but I too am interested
    in setting something like this up. Tony, do you want to work together
    on this?

    Sure, though I won't consider starting for a couple of weeks, I'm entering a particularly busy and important period.


    ... I used to think I was vague ... but now I'm not so sure!!!!!
    --- MultiMail/Win32 v0.49
    * Origin: Freeway BBS - freeway.apana.org.au (3:633/410)