Just a sample of the Echomail archive
Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.
|    BINKD    |    Support for the Internet BinKD mailer    |    8,958 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 8,032 of 8,958    |
|    Michiel van der Vlist to Binkd Team    |
|    Extended bindaddr    |
|    19 Jun 22 12:18:16    |
      TID: FMail-W32 2.1.3.7-B20170919       TZUTC: 0200       CHRS: CP850 2       PID: GED+W32 1.1.5-b20170303       MSGID: 2:280/5555 62aef7e9       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              ---        * Origin: http://www.vlist.eu (2:280/5555)       SEEN-BY: 1/123 15/0 90/1 103/705 105/81 106/201 114/705 709 120/340       SEEN-BY: 123/120 131 124/5016 129/305 330 331 153/757 7715 154/10       SEEN-BY: 203/0 218/700 840 220/70 221/0 6 226/17 30 227/114 229/110       SEEN-BY: 229/111 112 113 200 206 307 317 424 426 428 470 550 664 700       SEEN-BY: 240/5832 250/5 8 266/512 267/800 280/464 5003 5555 282/1038       SEEN-BY: 292/854 8125 298/25 301/1 305/3 310/31 317/3 320/219 322/757       SEEN-BY: 341/234 342/200 396/45 423/120 460/58 633/280 712/848 770/1       SEEN-BY: 770/100 340 772/210 220 230 2452/250 5019/40 5020/1042 5053/58       PATH: 280/5555 464 770/1 317/3 229/426           |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca