• frozen@lemmy.frozeninferno.xyzEnglish
    21·
    1 year ago

    The solution to fix my development environment at my old job was disabling IPv6. Gives a good insight into the quality of the software…

  • remram@lemmy.mlEnglish
    142·
    1 year ago

    For whatever reason, to this day I get a 403 error on http://google.com/ from IPv6. https://www.google.com/ works through.

    Sometimes it’s not your side that is broken.

    • SteveTech@programming.devEnglish
      5·
      1 year ago

      http://google.com/ works fine for me, tested in Firefox and with curl -6. So it could actually be your side that is broken, although it is probably your ISP’s.

      • remram@lemmy.mlEnglish
        2·
        1 year ago

        My side works fine, Google just doesn’t like the address. It’s a tunnelbroker address, maybe they consider that bots… but only for some of their servers? It’s weird

        • SteveTech@programming.devEnglish
          21·
          1 year ago

          Oh okay, IMO IPv6 tunnels are worse than just disabling it, because it’s basically just a proxy with IPv6, and since there’s no encryption (at this layer) both your ISP and now the tunnel could collect your data, as well as added latency.

          But I guess it’s okay for experimentation or if you actually require IPv6 for something.

          • remram@lemmy.mlEnglish
            4·
            1 year ago

            Hard disagree there. It is a tunnel, it is plenty fast if the intermediate node is close enough, and why would you want encryption at the IP layer.

            It works great and gives me IPv6 that I otherwise wouldn’t have with my ISP (Optimum), allowing me to connect to native IPv6 site and use all the IPv6 functionality I want (dedicated IPs for containers/VMs etc).

  • itsmikeyd@lemmy.mlEnglish
    9·
    1 year ago

    I have all sorts of weird troubles with IPv6 at home. Facebook won’t load some content, Netflix will frequently buffer and fail to load, Steam will almost never download things quickly.

    Turn off IPv6 on my router, all my troubles go away.

    • gogozero@lemmy.sdf.orgEnglish
      6·
      1 year ago

      sounds like it may be a wonky dns server. if youre interested, try re-enabling ipv6 but use something like cloudflare’s dns in lieu of your ISP’s

    • AggressivelyPassive@feddit.deEnglish
      1·
      1 year ago

      I have one, they’re awesome.

      I MacGyvered a 2.5" HDD into it and idling it draws 5W, while my pi 3 draws 4-5W, so definitely worth a try, if you can get a cheap one.

  • normonator@lemmy.mlEnglish
    6·
    1 year ago

    I’m in Canada and none of the 3 ISPs I have available support ipv6 even on business connections.

    You can probably guess the three and be wrong but also right, this is the case lots of places in Canada only less options.

  • catacomb@beehaw.orgEnglish
    2·
    1 year ago

    Weird to see this, I had to do it this morning!

    I have a fix to enable IPv6 but I’ll do it after hours :)

  • o_p@lemmy.mlEnglish
    2·
    1 year ago

    Used to have an MSI wind back in the day, this looks exactly like it!

  • fubo@lemmy.worldEnglish
    1·
    1 year ago

    For a little historical context:

    • IPv6 became a draft standard in 1998, and did not officially lose the “draft” status until 2017.
    • Hurricane Electric launched their well-known IPv6 tunnel service in 2001.
    • Google has published IPv6 adoption stats since 2008. These stats consistently show a greater fraction of users are on IPv6 on the weekend, because it’s more common on mobile and home networks than office networks.