4 ms·

I always disable IPv6 at home and computers I administer. IPv6: for machines (IoT) IPv4: for humans

• philjohn 8y ago
  if it doesnt do ipv6 it's broken
  • donatj 8y ago
    I think that is an overstatement. A car is not broken because it does not drive on rail, you can get you to the same places. There is currently very little you cannot do without IPv6.
    • philjohn 8y ago
      It's a well known quote. There are ways to solve the IPv6 problem - and ISPs in Europe have successfully rolled out both major variants, Dual Stack (Native IPv4 and v6 running alongside each other) or DSLite (Native IPv6 throughout the network, CGNat at the edge for tunnelled IPv4 traffic). Liberty Global have opted for DSLite, the last major network of theirs will go live this year (Virgin Cable), BT and Sky (the two biggest xDSL providers) have been live for over a year at this point with Dual Stack.
  • geofft 8y ago
    The article says the exact opposite: if it doesn't do IPv4 (either on its own, or via reliance on a NAT somewhere) it's broken.
• dpark 8y ago
  IPv4 is for machines. IP addresses were never intended for humans, which is why domain names exist.
  • Pxtl 8y ago
    Except that setting up domain names for devices in your network is out of reach for most humans, while IP addresses are trivial. My cheap router that I have to reboot nightly lets me bind an ipv4 address to every device on the network so I have known address for everything. There is no comparable functionality for a domain name, or a subdomain or whatever. If my ISP offered free dyndns (and there was a well-adopted global standard for the service), and I could assign subdomains for each of my devices, then I could have real names for everything. However, no consumer-level router supports that.
    • rleigh 8y ago
      Most common routers and systems will automatically register and resolve names automatically on the local network. Plus there's zeroconf on top of that. You don't need to manually edit bind zone files for your local network unless you really want to.
      • Pxtl 8y ago
        I have literally never ever seen a cheap consumer router that did anything "automatically" successfully other than run DHCP and provide access from the LAN to the WAN.
        • rleigh 8y ago
          The last two I've used over the last decade have automatically done this. Every machine requesting a DHCP lease is assigned "$host.lan" in the DNS service on the router, where "lan" is a default but configurable domain name. But even if you don't have this, then zeroconf/avahi/equivalent should be giving you "$host.local".
    • mdaniel 8y ago
      > If my ISP offered free dyndns I am about 80% certain that in the time it took you to write this comment you could have bought a domain name, used the registrar's web-gui to input your now static IP addresses, and had a perfectly functioning DNS setup for your home. Or, if the free DDNS is the most important to you, OpenWRT appears to natively support quite an extensive list: https://openwrt.org/docs/guide-user/services/ddns/client https://openwrt.org/docs/guide-user/services/ddns/client