= Сообщение: 5786 из 7402 ============================================= IPV6 = От : Michiel van der Vlist 2:280/5555 08 Dec 18 19:51:55 Кому : Kees van Eeten 08 Dec 18 19:51:55 Тема : New in this FGHI : area://IPV6?msgid=2:280/5555+5c0c14ba На : area://IPV6?msgid=2:280/5003.4+5c0bfe32 = Кодировка сообщения определена как: CP850 ================================== Ответ: area://IPV6?msgid=2:292/854+171b1a4d ============================================================================== Hello Kees,
On Saturday December 08 2018 18:23, you wrote to me:
MvdV>> But where does the configuration file for binkd come from? Is MvdV>> it created totally seperated from D'Bridge or does D'Bridge MvdV>> write to binkd's config file?
KE> Dbrige is just as much involved in the actions as your Fmail. Ward KE> uses a separate configfile, but the one dbrigde generates is perfectly KE> well, it works here for almost a year. So harping on dbridge is a KE> waste of time.
I was not harping on D'Bridge, I was trying to pinpoint the source of the problem by elimination. The inner workings of D'Bridge have always been treaetd as if they are state secrets. So I had to work on a minimum of knowledge.
KE> Dbrigde is a scanner, tosser, message editor, scheduler and pots KE> mailer. There is no other connection that BSO file area and semaphore KE> files.
OK...
MvdV>> The latest binkd release that I use is MvdV>> binkd11a99-mingw32-ipv6-perldl-zlib-bzlib2.zip
KE> The last few versions were just addition of useless options.
When encountering problems, it is always a good strategy to try the latest version. Whether one needs it or not. The latest version is the only one that is maintained.
KE> Almost nay available version shoild wordk with ipv6 as long as it is KE> compiled in.
The way it looks now, is that the version of binkd that Ward used was the exception. Despite the fact that it showed the IPv6 compile option was used, it would not do IPv6. So replacing it was NOT useless in tracing the problem.
