= Сообщение: 820 из 7442 ============================================== IPV6 = От : Michiel van der Vlist 2:280/5555 24 Jul 14 00:21:01 Кому : Alexey Vissarionov 24 Jul 14 00:21:01 Тема : Testing with BinkD... FGHI : area://IPV6?msgid=2:280/5555+53d037d9 На : area://IPV6?msgid=2:5020/545+53cf3aec = Кодировка сообщения определена как: CP850 ================================== ============================================================================== Hello Alexey,
On Wednesday July 23 2014 08:20, you wrote to Benny Pedersen:
BP>> for nodelist data use: BP>> root-domain binkp.net BP>> node 2:230/0 * password
AV> Very dangerous advise. All persistent links _should_ be defined AV> explicitly, otherwise you may end up with no connectivity once AV> something will happen to root-domain (as it once happened to AV> fidonet.net).
True. OTOH, very few IP mailers follow the nodelist. So if you explicitly define the host name in the mailer config, it will not automatically be updated when it changes in the nodelist and connectivity with that node will be lost. It will not be restored until the sysop intervenes by manually editing the mailer's config file. We have seen examples of this when dyndns changed its policy and many sysops had to change their host names.
binkp.net DOES follow the nodelist, so With the binkp.net method this problem is avoided.
Each mathod has its pros band cons.
BP>> then binkp will try ipv4/ipv6 as /etc/gai.conf says if node is BP>> dual stacked
BP>> default is btw ipv4 first, this is not a fault !
AV> It is. IPv6 _must_ be tried before IPv4. Changing this precedence is AV> possible, but not advised outside of LANs.
Opinions differ. Ever heard op happy eyeballs?
For FOIP it is no big deal if there is a 60 second delay because the nodelist advertises IPv6 connectivity but it is not there and it only falls back to IPv4 after a time-out. For other applications this can be a show stopper.
