= Сообщение: 4310 из 7440 ============================================= IPV6 = От : Michiel van der Vlist 2:280/5555 25 Apr 17 15:23:47 Кому : Kees van Eeten 25 Apr 17 15:23:47 Тема : IPv6 only node? FGHI : area://IPV6?msgid=2:280/5555+58ff500b На : area://IPV6?msgid=2:280/5003.4+58ff3b3f = Кодировка сообщения определена как: CP850 ================================== ============================================================================== Hello Kees,
On Tuesday April 25 2017 13:55, you wrote to me:
MvdV>> Binkd when on an IPv4 connection, will keep trying to connect MvdV>> to 2:221/10 until the sysop or other software intervenes.
KE> I would like to disagree with you, that Binkd keeps on trying a IPv4 KE> connection if only an IPv6 address is available.
Maybe I expressed myself poorly. It does indeed not try to connect via IPv4. But it does try to connect. Or at least initiate an attempt to connect. It keeps on doing that every minute until the max nr of failed connections is reached. Then it puts the mail on hold for some time and when that time has elapsed, it goes on trying again. Ad nauseum..
KE> Moreover, Binkd has no knowledge of the Nodelist. It is the task of KE> the intermediate software, that converts te Nodelist to Binkd's KE> version to translate the INO4 to a "-6", or to exclude the node if the KE> list is prepared for a ipv4 only node.
That is more or less what I meant by:
MvdV>> The INO4 flag is still usefull in this case as it allows more MvdV>> intelligent agents to avoid or remedy the above situation.
Higher level sofware can use the INO4 flag to see that binkd never even tries. By either putting the mail on Hold, so that the other side can come pick it up, or by seeing that mail for the node in question is routed and not send direct. Of course the IN4 flag can also be of use to the human overseeing it all...
