Posts: 272
Threads: 25
Joined: Aug 2010
Posts: 534
Threads: 21
Joined: Jun 2010
22 May 11, 11:54PM
(This post was last modified: 22 May 11, 11:55PM by Zarjio.)
I shouldn't affect AC much at all. Fact is, more and more hardware is being created that is IPv4 and IPv6 compliant, and we will gradually see IPv4 fade away. AC will continue to use UDP, which will be unchanged by the switch over to IPv6. Some variable might need to be re-assigned because the addresses are now 64 bit instead of 32 bit, that should be all.
Essentially, the difference between IPv4 and IPv6 is that IPv4 has 32 bit addresses and allowed for options fields in the header, while IPv6 has 64 bit addresses and has phased out the options field.
Posts: 241
Threads: 3
Joined: Jun 2010
128 bit
For AC, the network library should be updated if it doesnt already support v6.
Posts: 3,780
Threads: 33
Joined: Jun 2010
I kind of wondered myself, will it still show IPv4 addresses when you /whois someone?
Posts: 534
Threads: 21
Joined: Jun 2010
Ah, 128 bit. Apparently I was not paying enough attention during my networking class :p
I would imagine that the /whois could be made to show IPv4 or IPv6, whatever the client is connecting with (and IPv6 if they have both addresses).
Posts: 3,780
Threads: 33
Joined: Jun 2010
23 May 11, 04:18PM
(This post was last modified: 23 May 11, 04:22PM by V-Man.)
Is the game already configured to handle IPv6 whois info?
After looking at the code, it seems to me that /whois only prompts the engine to process four octets. Makes me wonder what it would do with "fe80::202:b3ff:fe1e:8329"...
Edit:
Quote:I would imagine that the /whois could be made to show IPv4 or IPv6
I see now, you mean the game could be changed in the future to allow /whois to handle both. XD
