= Сообщение: 2616 из 7440 ============================================= IPV6 = От : Kees van Eeten 2:280/5003.4 25 Apr 16 12:31:48 Кому : Markus Reschke 25 Apr 16 12:31:48 Тема : IPv6 problems FGHI : area://IPV6?msgid=2:280/5003.4+571df5f1 На : area://IPV6?msgid=2:240/1661+56d19830 = Кодировка сообщения определена как: LATIN-1 ================================ ============================================================================== Hello Markus!
25 Apr 16 11:20, you wrote to me:
MR> Yep, some like them included, others don't. I could add a switch for MR> filtering them to please all.
Well, don't listen to me, I roll my own anyway.
KvE>> I get fewer lines, as I exclude lines where Hostnames does not KvE>> resolve.
MR> Could be another switch :) But I'm not sure, because a node could have a MR> boken DNS entry today and have it fixed by tomorrow.
I derive my "binkd.txt" file from the daily nodelist.
MR> Or the entry could be broken for several months.
And years, those show up in my regular nag lists. ;)
MR> We simply don't know. And even if the entry MR> resolves it doesn't mean that the IP address is correct. Actually we MR> would MR> also have to check if a binkd is listening.
That is still on my todo list. I am still hesitating as the methods available are quite intrusive, even when stealth modes are used.
MR> Same story here, binkd might MR> be crashed today and fixed by tomorrow or the IP address could be MR> wrong. MR> How should we deal with these nodes?
In the end Binkd has the last word. If it cannot connect, it will not deliver. Observing the outgoing queue will tell you that something is wrong.
As an aside I do add the "-6" flag in a separate process, for those nodes, where their implemantation if IPv6 defaults to using IPv4 first. Unfortunately a manua list must be maintained to accomplish that.
Kees
--- GoldED+/LNX 1.1.5 * Origin: As for me, all I know is that, I know nothing. (2:280/5003.4)
