LAG issue - HowTo solve it

voobscout · Post by **voobscout** » Mon May 04, 2009 4:50 pm

yes, everything is in progress, but i have to finish up some RL work before i can devote more time to alleg ipv6, i can only say, that within [2..4] days, everything will be ready to test, including nice feedback form etc... plus ofcourse clear instructions for those who have none-IT mindsets...

Dogbones · Post by **Dogbones** » Tue May 05, 2009 2:39 pm

Jeruwafi wrote:QUOTE (Jeruwafi @ May 4 2009, 12:41 PM) IIRC w2k ipv6 preview requires some hex editing before install to make it fully compatible with current standards (rDNS issue iirc) :]

That is exactly the problem. It is only an issue for those running Win2K SP4. If you are running SP2 the package from MS loads without a hitch. MS does not support ipv6 on Win2K (or earlier if at all) beyond this 'preview' so they never updated the installer.

Post by **FreeBeer** » Wed May 06, 2009 4:09 am

Doubt that it's a real problem for Alleg. The 2.2 version of ASGS is incompatible with Win2k.

w0dk4 · Post by **w0dk4** » Sun May 10, 2009 3:05 am

QUOTE If only some of my clients were THAT fast to move on useful things as alleg community....[/quote]

dont hold your breath

Traxi · Post by **Traxi** » Sat Aug 15, 2009 3:40 pm

So how is the Alleg IPv6 progressing ?
The current popular Solap server can use some workaround routes, due to extreme lags in certain cases to it.
(not sure if the workaround will work for the most cases of lag on that server, due to the exact position of the problematic router(s) in the chain.
But surely wont hurt to try ?

)

Imago · Post by **Imago** » Sun Aug 16, 2009 12:41 am

According to this: http://download.microsoft.com/download/B/0...MC-DPLHP%5D.pdf DirectPlay 8 works fine with IPv6.

Alleg uses DirectPlay8 but there are a few places in the code (outside of DirectPlay) where IPv4 addresses are expected, I believe all of these are FAZ Dev changes (i.e. not msoriginal) which will get in the way of Alleg running on an IPv6 host.

Don't forget about the Lobby, it too will probably need an IPv6 address for things to work /w minimal code changes.

Imago · Post by **Imago** » Mon Aug 17, 2009 2:06 pm

gah

Code: Select all

PING 2001:470:7:56b::2: 56 data bytes

----2001:470:7:56b::2 PING Statistics----
5 packets transmitted, 0 packets received, 100% packet loss

Code: Select all

PING ipv6.google.com: 56 data bytes
64 bytes from fx-in-x68.google.com (2001:4860:a003::68): icmp_seq=0. time=105. ms
64 bytes from fx-in-x68.google.com (2001:4860:a003::68): icmp_seq=1. time=105. ms
64 bytes from fx-in-x68.google.com (2001:4860:a003::68): icmp_seq=2. time=104. ms
64 bytes from fx-in-x68.google.com (2001:4860:a003::68): icmp_seq=3. time=105. ms
64 bytes from fx-in-x68.google.com (2001:4860:a003::68): icmp_seq=4. time=104. ms

----ipv6.google.com PING Statistics----
5 packets transmitted, 5 packets received, 0% packet loss
round-trip (ms)  min/avg/max/stddev = 104./105./105./0.62