URL:
  <http://gna.org/task/?7954>

                 Summary: IPv6 metaserver
                 Project: Freeciv
            Submitted by: cazfi
            Submitted on: Sat 07 Nov 2015 01:23:17 PM EET
         Should Start On: Sat 07 Nov 2015 12:00:00 AM EET
   Should be Finished on: Sat 07 Nov 2015 12:00:00 AM EET
                Category: None
                Priority: 5 - Normal
                  Status: None
                 Privacy: Public
        Percent Complete: 0%
             Assigned to: None
             Open/Closed: Open
         Discussion Lock: Any
                  Effort: 0.00
         Planned Release: 

    _______________________________________________________

Details:

This is tracking ticket for the (default) metaserver & IPv6 issues. I'm not
expecting this to get fully resolved soon.

So far:
- The metaserver code has had IPv6 support for some time, and it exist in both
branches (the main branch, and legacy one compatible with older php-versions)
- Freeciv itself has had IPv6 support several versions already. (Not sure if
it was first introduced in 2.1 or 2.2) Anyway, 2.0 used by the warserver
people doesn't have it.
- The Windows version *still* doesn't have IPv6 support. We hope to get it in
2.6.
- I run test IPv6-only metaserver on cazfi.net for some years, but it's now
defunct
- We have no IPv6 enabled server to run metaserver on

While we can have different test setups with IPv6-only metaservers, for the
final switch of the default metaserver, there's one big issue to be solved;
interactions where IPv4-only and IPv6 enabled freecivs are involved.
Metaserver can't just give out IPv6 address of the freeciv server to the
IPv4-only client.




    _______________________________________________________

Reply to this item at:

  <http://gna.org/task/?7954>

_______________________________________________
  Message sent via/by Gna!
  http://gna.org/


_______________________________________________
Freeciv-dev mailing list
Freeciv-dev@gna.org
https://mail.gna.org/listinfo/freeciv-dev

Reply via email to