Most routers made after 2006 support IPv6 either natively or via firmware upgrades, so hardware really isn't an issue anymore.
I have deployed it before without any notable issues. We setup DNS records to point towards the LAN behind a static IPv6 address, and had no trouble connecting from the WAN. The ISP gave us a static IPv4 address as a rollback as well.
As you noted, other applications seem to suffer from IPv6 compatibility, but the FM portion of our deployment worked fine. If I recall, we let the ISP deal with the initial config of the router to work out any issues on the WAN connection, then we came in after and set up everything for FMS.
I assume this was FM13. What OS? Did you try ODBC, CWP, WebDirect and Go with it too? Thanks for sharing whatever you tried. I appreciate your feedback, Mike! Looking forward to seeing you at Devcon.
it was back in FMS12. We used Go12 without issue as well, no CWP/IWP/ODBC testing.
I just recall that there were more hassles with the ISP (time warner) than there was with the FMS setup.
I would think that DNS (domain name servers) would be your best friends here, IF you use domain names and not IP addresses for any call to FMServer.
Good point, Beverly. And I almost always do use URL's instead of IPs because when I move a server to a new IP or ISP, I don't have to do anything with the clients. Most of my small clients that have DNS are doing it on Mac OS X Server. I need to go confirm if there is anything I need to do with those to make sure the DNS in the Server.app works fine with IPv6 or if I need to change anything.