Stories
Slash Boxes
Comments

SoylentNews is people

SoylentNews is powered by your submissions, so send in your scoop. Only 14 submissions in the queue.
posted by NCommander on Tuesday April 01 2014, @12:00PM   Printer-friendly
from the there-was-much-rejoicing dept.
As part of wanting to be part of a brighter and sunny future, we've decided to disconnect IPv4 on our backend, and go single-stack IPv6. Right now, reading to this post, you're connected to our database through shiny 128-bit IP addressing that is working hard to process your posts. For those of you still in the past, we'll continue to publish A records which will allow a fleeting glimpse of a future without NAT.Believe it or not, we're actually serious on this one.

Linode IPv6 graph

We're not publishing AAAA records on production just yet as Slash has a few minor glitches when it gets an IPv6 address (they don't turn into IPIDs correctly), though we are publishing an AAAA record on dev. With one exception, all of our services communicate with each other on IPv6.

Perhaps I will write an article about our backend and the magical things that happen there :-).
 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 1) by Nesh on Tuesday April 01 2014, @12:48PM

    by Nesh (269) on Tuesday April 01 2014, @12:48PM (#24091)

    if you actually offered IPv6 to start with.

    I understand it's not a top priority.
    As a site for geeks you might consider it.

  • (Score: 2) by NCommander on Tuesday April 01 2014, @12:56PM

    by NCommander (2) Subscriber Badge <michael@casadevall.pro> on Tuesday April 01 2014, @12:56PM (#24103) Homepage Journal

    Its actually been on the TODO list from day one. The problem is that Slash creates IPID instead of storing raw IP addresses. This has some glitches when it gets an IPv6 address vs. IPv4; its at the point the site no longer explodes in flames, but we don't get a valid SUBID, which causes issues with cookies. This code probably needs a rework to be fully IPv6 complaint.

    That being said, it has no problems talking to the database over IPv6.

    --
    Still always moving
    • (Score: 1) by Nesh on Tuesday April 01 2014, @01:11PM

      by Nesh (269) on Tuesday April 01 2014, @01:11PM (#24117)

      I can believe you don't have any problems talking to the database over IPv6.
      Linode VMs are now native IPv6 enabled and it works good.
      Before that time we had to use a 6in4 broker to get IPv6 working on a Linode VM.

      This may be a good place to refer to the nice people at HE [he.net]
      (not affliated in any way) for people that want to learn about and do more with IPv6.

      The free hands-on certification [he.net] is excellent and fun to do.
      If your provider lacks native IPv6 support, their free tunnelbroker [tunnelbroker.net] is a good help.
      The 6in4 tunnel adds latency but it's good enough to get started with.

      • (Score: 2) by NCommander on Tuesday April 01 2014, @01:21PM

        by NCommander (2) Subscriber Badge <michael@casadevall.pro> on Tuesday April 01 2014, @01:21PM (#24128) Homepage Journal

        Actually, when we yanked out the old A records, the only thing that didn't quite work was MySQL as it doesn't listen on IPv6 by default. That required one line in its config file:

        bind-address = ::

        Which set it to bind IPv6 only. I wanted to post the netstat output, but it seems it has too many colons and the lameass filter won't let it through.

        --
        Still always moving