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,528 of 8,958    |
|    Michiel van der Vlist to Binkd Team    |
|    Extended bindaddr    |
|    07 Nov 23 17:24:07    |
      TID: FMail-W32 2.2.0.0       TZUTC: 0100       CHRS: CP850 2       PID: GED+W32 1.1.5-b20170303       MSGID: 2:280/5555 654a64aa       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/19 123 15/0 16/0 19/37 40 90/1 103/705 105/81 106/201 123/130       SEEN-BY: 123/131 124/5016 129/305 132/174 142/104 926 153/757 7715       SEEN-BY: 154/10 203/0 218/700 221/0 6 226/30 227/114 229/110 112 113       SEEN-BY: 229/200 206 275 307 317 426 428 470 550 664 700 240/1120       SEEN-BY: 240/2100 5411 5413 5824 5832 5853 6309 266/512 280/464 5003       SEEN-BY: 280/5555 282/1038 291/111 292/854 8125 301/1 305/3 310/31       SEEN-BY: 317/3 320/119 219 319 2119 322/0 757 341/66 234 342/200 396/45       SEEN-BY: 423/120 460/58 633/280 712/848 770/1 2432/390 2454/119 5019/40       SEEN-BY: 5020/400 1042 5053/58 5075/35       PATH: 280/5555 464 240/5832 320/219 229/426           |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca