Hello Alex,

On Sunday January 21 2018 22:46, you wrote to me:

 AS> Well, remembering my XP days, IPv6 stuff was in alpha/beta state
 AS> there. And network stack was pretty buggy. Got "No buffer space
 AS> available" after couple of days uptime and forced to reboot too.

Yes, the IPv6 implementation of XP is incomplete (no DHCP6) and it is a bit 
buggy. It works good enough to run a Fdionet IOv6 node though.

 AS> Win7 will definitely work better with this.

Perhaps it is time to say goodbye to XP?

 MvdV>> From the log it seems some IPv6 is coming in, but it would be
 MvdV>> nice of someone would see if they can reach www.vlist.eu via
 MvdV>> IPv6

 AS> It works.

Thanks, The odd thing is that I can connect to my web server locally via IPv6, 
but the connection via IPv4 seems to be the prefered one. To connect via IPv6 I 
must force an IP6 connection by using a host name without an IPv4 address. 
Maybe the relay introduces a delay that makes IPv4 preferent on the otherwise 
fast local connection?

 AS> I see you have native IPv6, too:

Yes, since mid 2016.

 AS> ipv6.dynamic.ziggo.nl [2001:1c02:1100:d700:f1d0:2:280:5555]

 AS> but your ISP does not seem to assign proper reverse DNS for customers.

Indeed, that is a bit of a joke. Every IPv6 addres (2001:1c02::/32) of my 
provider backresolves to ipv6.dynamic.ziggo.nl.


Cheers, Michiel

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