Hello Andrei,

Saturday April 28 2018 22:08, I wrote to you:

 MV> When I do not run the server and just start the client with:

 MV> binkd-static -pP5020/9696 binkd.cfg

 MV>   then the -4 -6 -46 and -64 commands work as expected.

More testing...

Not only should it try IPv6 first with -64, it should also fall back to IPv4
when the IPv6 connection fails. To test this I created a DNS entry for:

skovpen.vlist.eu.

It has an A record the same as skovpen.org. The AAAA record is increased by 1.
So an attempt to connect to skovpen.vlist,eu via IPv6 will fail.

Note that the AAAA record is in the 6to4 range (2002::/16). So the OS
preference is IPv4 first. (For windows)

In the binkp config I changed the host name for 5020/9696 to skovpen.vlist.eu

I tried all five options of , -64, -46, -6 and -4.

   Client calls out on IPv4 and succeslfully connects.

-64      Client tries IPv6. Timeout. Tries IPv4 and succesfully connects

-46      Client calls out on IPv4 and succeslfully connects.

-6       Clients tries IPv6 and fails. No attempt to try IPv4.

-4       Client calls out on IPv4 and succeslfully connects.


This is exactly how it should work. Feel free to use skovpen.vlist.eu to try to
repeat my findings,

I will test the server mode next...

Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303