IPv6 Compatibility

[_Varis_]

Going into the future, we need to answer an important question - are the Kal executables compatible with IPv6?

For those of you who don't know, we are currently on IPv4: each IP address has four octets (255.255.255.255). IPv6 adds another two octets: 255.255.255.255.255.255.

I don't have the proper hardware to be able to test if there is compatibility. If there isn't, my question to you is - what are we going to do about it?

The possibility crossed my mind of perhaps creating a utility that proxies outside packets, translating them to virtual internal IP addresses so that the utility listens on, say, port 30001 and sends translated traffic to port 30002, where the Kal server is listening.

Granted, this switchover isn't going to happen for a few years yet, but I'm interested in seeing what you guys are planning to do for it, or if you have any better ideas than me, or better yet - I want to see if the Kal server is already IPv6 compatible.

-V

 

[General]

If IPv6 ever comes, kal will be long forgotten if no new server files are released.

 

[spicman]

If IPv6 ever comes, kal will be long forgotten if no new server files are released.

I am in the IT business and we roll out Windows 2008 servers and just like Vista (and upcoming Windows 7) its preconfigured with IPv6 running so IPv6 IS HERE :8:

Whether or not all are adapting this new scheme is another thing.

Going into the future, we need to answer an important question - are the Kal executables compatible with IPv6?

For those of you who don't know, we are currently on IPv4: each IP address has four octets (255.255.255.255). IPv6 adds another two octets: 255.255.255.255.255.255.
-V

Just to clarify, IPv6 addresses are normally written as eight groups of four hexadecimal digits, where each group is separated by a colon ). And one or any number of consecutive groups of 0 value may be replaced with two colons . If you have Windows Vista open up a CMD prompt and type IPCONFIG

You SHOULD see one of your configs show the following:

Link-local IPv6 Address . . . . . : fe80::cc91:8665:6cfb:72dc

And yes IPv6 is backward compatible with IPv4.

Having said all this it shouldnt be that difficult to test. On Vista you can setup a server and make sure you disable IPv4. If you are planning (or have running Windows 2008) you could do the same thing. I currently have both Windows 2008 Enterprise and Vista which I could do this on and report back

That's my 2cents worth.

Cheers!

 

[_Varis_]

I currently have both Windows 2008 Enterprise and Vista which I could do this on and report back

That'd be great, if you can. And thanks for the correction. :

-V

 

[DeathArt]

The IPv6 protocol implements a wrapper for the IPv4 package format, so there's no need to worry.

And you can get around the IPv4 requirement in the configuration files (config.pk) by using hostnames rather than direct IPs, then your DNS will translate it for you, and KalOnline won't notice a difference.

As for internal host names, if you're to lazy to set up a internal DNS server, just use the HOSTS instead.

 

[spicman]

Not to be lazy or not want to try it...but DeathArt gave a better answer :

Cheers!

 

[DeathArt]

I'm also quite certain that Inixsoft uses a outdated networking library without direct IPv6 address support.

 

[_Varis_]

I'm also quite certain that Inixsoft uses a outdated networking library without direct IPv6 address support.

As am I - as evidenced by my concern.

So the overall vibe I'm getting from the responses is to simply not worry about it. I'm good with that.

-V