PtokaX forum

Development Section => PtokaX Development Versions => Topic started by: PPK on 15 October, 2011, 04:33:34

Title: 0.4.2.0 build 301
Post by: PPK on 15 October, 2011, 04:33:34
Windows x86/x64 version with GUI: http://www.PtokaX.org/files/0.4.2.0b301.7z
Windows x86/x64 service: http://www.PtokaX.org/files/0.4.2.0b301-service.7z
Source is in SVN (http://forum.ptokax.org/index.php?topic=7821.0)

Quote from: Changes from build 258
Added: IPv6 support to sockets.
Added: IPv6 support to bans and range bans.
Added: IPv6 country database support.
Added: IPv6 client to client connections support.
Added: IPv6 search support.
Added: IP64 and IPv4 protocol extensions support.
Added: Check for IPv4 connection for user connected to hub by IPv6.
Added: IPv4 client connection support for users connected to hub by IPv6 when IPv4 connection check success.
Added: IPv4 search support for users connected to hub by IPv6 when IPv4 connection check success.
Changed: Country database for IPv4 from ip-to-country to IpToCountry.
Fixed: TmrMan.RemoveTimer Lua api call in windoze version (thx Cęńo?y?ę for report)

Major change to this testing is IPv6 support. It is enabled automatically when OS support it and have support for dual-stack sockets. That means it is not working on windoze older than Vista :P

With IPv6 support we have support for new Country databases. You can download them on http://software77.net/geo-ip/ ::) For IPv4 you need IPV4 CSV (gz) and for IPv6 you need IPV6 Range (gz). Unpack them to PtokaX cfg dir ;)

I'm added two protocol extensions for good IPv6 support (full docs will be available later).
First is 'IP64', that one do "magic" and in simply way show who support IPv4 and who IPv6. That way IPv6 users can correctly connect only to IPv6 users.
Because it will be stupid to have hub divided to IPv4 and IPv6 users where IPv4 can download only from IPv4 and IPv6 only from IPv6 i'm added second protocol extension.
So second protocol extension is 'IPv4'. This one is only for users who connect to hub using IPv6. Client send this support when he support IPv4 and hub is responsible to check his IPv4 connection and when check success then allow him to use IPv4 connections. It is expected that most IPv6 users have IPv4 connection available (simply because 99.9% of internet is IPv4) so i want to allow users who connected to hub with IPv6 to connect to IPv4 users and of course IPv4 users can connect to those IPv6 users. Limited connectivity will be only for IPv6 users without IPv4 support, they will be able to make connections only to IPv6 users :(

Important thing to allow IPv4 check for users connected by IPv6 is correct IPv4 address on hub, so please set correct hub address because without that check will fail.

I'm running test hub with IPv6 enabled on address dchub://ipv6-test.czdc.org 8)
Title: Re: 0.4.2.0 build 301
Post by: PPK on 15 October, 2011, 22:16:38
When is nice to have IPv6 support in hub, it is nothing without IPv6 supporting client. So client with IPv6 support is available on http://www.czdc.org/forum/index.php?topic=3971.0 8)
Title: Re: 0.4.2.0 build 301
Post by: somewherenotthere on 29 November, 2011, 12:40:52
I love you man  ;D ;D :-\