• Extended bindaddr

    From Michiel van der Vlist@2:280/5555 to Binkd Team on Sat Oct 23 13:52:56 2021
    Hello Binkd Team,

    For many years I have been running several binkd nodes. One as my main Fidonet node, one as my mobile point and several test nodes. It works great.

    What I miss is a bit more flexibility regarding bindaddr.

    Bindaddr is used to specify the IP address to use for outgoing calls when there is more than one address avalable for the system. As it is, one can ony specify one address for all outgoing calls. What I would like to see is a way to use different addresses for different destinations.

    The first use case for bindaddr is of course ::f1d0. Presently I use:

    bindaddr [2001:1c02:1102:ac00:f1d0:2:280:5555]

    for my main node

    I can imagine a participant in another network would like to use something else for that other network. Such as:

    bindaddr [2001:1c02:1102:ac00:39:39:0:0] for use by the ZC of Amiganet.

    For testing within my own LAN I would like to be able to use local addresses. Usefull for testing in an environment where there is (deliberately or accdidentally) no internet connection. In addition to global IPv6 addresses I have assigned ULAs for my (test)nodes as well. So when possible and practical for my IPv6 only test node I use:

    bindaddr [fd51:550:40b9:0:f1d0:2:280:5556]

    (fd51:550:40b9::/48) is a ULA prefix that many years ago I registered with SixXs).

    So wouldn't it be nice if one could use more than one bindaddr keyword and add an FTN match to it. Like:

    bindaddr6 [fd51:550:40b9:0:f1d0:2:280:5556] 2:280/5555@fidonet
    bindaddr6 [2001:1c02:1102:ac00:f1d0:2:280:5556] *@fidonet
    bindaddr6 [2001:1c02:1102:ac00:ac0:77:8500:100] *@aconet
    bindaddr6 [2001:1c02:1102:ac00:21:100:1:0] 21:*
    bindaddr6 [::] *

    Binkd uses the address of the first match for the outgoing call.

    Cheers, Michiel

    --- Fmail, Binkd, Golded
    * Origin: http://www.vlist.eu (2:280/5555)
  • From Wilfred van Velzen@2:280/464.112 to Michiel van der Vlist on Mon Oct 25 09:50:32 2021
    Hi Michiel,

    On 23 Oct 21 13:52, Michiel van der Vlist wrote to Binkd Team:
    about: "Extended bindaddr":

    MvdV> @MSGID: 2:280/5555 61745a68
    MvdV> @PID: GED+W32 1.1.5-b20170303
    MvdV> @TID: FMail-W32
    MvdV> @TZUTC: 0200
    MvdV> @CHRS: CP850 2
    MvdV> @TID: FMail-W32
    MvdV> @TZUTC: 0200
    MvdV> @CHRS: UTF-8 4
    MvdV> @PID: GED+W32 1.1.5-b20170303
    MvdV> @MSGID: 2:280/5555 6173f798

    WTF! :-(

    MvdV> @PATH: 280/5555 464 770/1 317/3 15/0 261/38 301/1 280/464

    We've seen this before in another area, where kludges from another message are added to a forwarded message, and thus fooling the dupe checking. And there seems to be some seen-by stripping going on... :-(


    --- FMail-W32
    * Origin: point@work (2:280/464.112)