Stories
Slash Boxes
Comments

SoylentNews is people

SoylentNews is powered by your submissions, so send in your scoop. Only 11 submissions in the queue.
posted by takyon on Saturday January 19 2019, @01:19AM   Printer-friendly
from the ICUP dept.

A Swiss VM hosting provider has a technical blog post about how to kill IPv4 completely on FreeBSD. That is to say, turning it completely off, not just preferring IPv6. They then solicit concrete solutions describing, along with a proof of concept, how to turn IPv4 completely off in other operating systems and allowing them to communicate with IPv6 only.

Earlier on SN:
Vint Cerf's Dream Do-Over: 2 Ways He'd Make the Internet Different (2016)
You have IPv6. Turn it on. (2016)
We've Killed IPv4! (2014)


Original Submission

 
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: 2) by rleigh on Saturday January 19 2019, @05:35PM (1 child)

    by rleigh (4887) on Saturday January 19 2019, @05:35PM (#788701) Homepage

    Actually, it's far less bad than you say.

    Look into NAT64 and DNS64. You (or your ISP) sets up a proxy which maps a range of IPv4 addresses into the IPv6 address space. All DNS requests for an IPv4 host will return the mapped IPv6 address. All connections to IPv4 hosts use IPv6 to talk to the proxy, which then talks using IPv4 to the host in question. All your hosts internally are IPv6 only, but still transparently access the IPv4 network. You can even have it proxy for internal IPv4-only hosts as well on a private subnet, so you can keep legacy devices around. The reverse also applies; you can have external IPv4 connections proxy to an internal IPv6 host.

    This is a typical way you would set up a new network. It pushes IPv4 to the edge of your network, leaving the internal network with just IPv6 to support. It keeps things both simple and future proof. I definitely appreciate this for running virtual machines, which can bridge directly to the internal network with a global IPv6 address. No different than a regular host. Just maintain the appropriate firewall rules to control access, as you would for IPv4 with or without NAT.

    Starting Score:    1  point
    Karma-Bonus Modifier   +1  

    Total Score:   2  
  • (Score: 0) by Anonymous Coward on Saturday January 19 2019, @09:22PM

    by Anonymous Coward on Saturday January 19 2019, @09:22PM (#788770)

    Comcast and TW/Spectrum have native IPV6 stacks. AT&T not so much (as you have seen). Not sure on the VZ/Fronter setup currently as I have not seen it.