LAG issue - HowTo solve it

voobscout · Post by **voobscout** » Thu Apr 30, 2009 5:09 am

yes, silly me always forgets about APIs... however i can refer those "old" style apps to rfc 3089, the gist of it is to use socks to perform the translation, so even ugly code for ipv4 only, wouldn't need to be rewritten or recompiled...

voobscout · Post by **voobscout** » Thu Apr 30, 2009 8:23 am

well, since it's obviously rather hard to push current server admins into action regarding ipv6, not that they're unwilling or lazy, but probably just don't have the time for it. I decided to setup my own server with ipv6 and all the stuff i've been talking about.

i do have some spare bandwidth and a machine in one of my colos, so all i need now is for TE (i assume he's the guy for this) to allow my server to connect to lobby and I need instructions on how to actually setup a server, somebody suggested i follow 3fl thread, but searching forums for 3fl turned up 0 results (strange kinda).

So, if anybody would be so kind as to point me to the right instructions, wherever that might be... a post a thread on forums or a wiki, whatever it is, i'll setup a server with ipv6, hopefully TE will be gracious enough to let it connect to lobby and we'll start testing things....

badpazzword · Post by **badpazzword** » Thu Apr 30, 2009 8:24 am

Instructions to install and setup a server are located in the wiki.

Zapper · Post by **Zapper** » Thu Apr 30, 2009 4:10 pm

we could boot players with a lag of 100 or higher.. this way everyone will be happy

Archangelus · Post by **Archangelus** » Thu Apr 30, 2009 10:18 pm

This means BV would just perma-ban me.

voobscout · Post by **voobscout** » Sun May 03, 2009 11:30 am

Here's a small update:

DB kindly decided to have ipv6 implemented at one of the beta servers, so soon we'll be able to perform real end2end connectivity testing and everyone will be able to figure out if ipv6 is for him/her.

Thank You, DB !

Dogbones · Post by **Dogbones** » Mon May 04, 2009 2:49 am

Should be all set. voob and I have been in PM contact.
You will need to run the R5 beta version of Allegiance to connect to the beta server.

There are instructions in the dev forum in the sticky on how to do this. If you've tried the beta before it is pretty easy to just get the latest client, if you have not there may be some additional steps involved.

http://www.freeallegiance.org/forums/index...showtopic=44386

Note the version of the beta in the sticky may not be the correct one. It won't make a difference for this test.

TheCorsair · Post by **TheCorsair** » Mon May 04, 2009 5:51 am

Thanks heaps Dogbones.

Given I'm on mostly late night like yourself Voobscout, I'm happy to test/trial it out with you.

Just give me a holler.

My only concern with R5 beta is the issues I posted in the relevant threads re crashing to desktop when I'm in F3.

voobscout · Post by **voobscout** » Mon May 04, 2009 3:55 pm

Good news everybody, the real fazdev ipv6 is ONLINE and is waiting for you guys to test connectivity to it. I'll update my google forms accordingly with more clearer instructions etc... meanwhile, to quote venerable DB:

So the IPv6 address of the fazdev machine is 2001:470:7:56b::2
The regular ip address is 12.96.40.28 (or fazdev.alleg.net)

---
Apparently w2k sp4 has some unforseen issues, nothing serious, but according to DB, he had some minor trouble getting ipv6 up and running, i'll investigate it within the next couple of days, maybe i'll even ask Dog to get me his VM image of the machine, so i can poke around in it.... we'll see

Jeruwafi · Post by **Jeruwafi** » Mon May 04, 2009 4:41 pm

IIRC w2k ipv6 preview requires some hex editing before install to make it fully compatible with current standards (rDNS issue iirc) :]

Can we get more detail about the server?
What broker does it use (if any

)?
How to connect (I guess it's in progress

)?
Should we know about anything?

:]