• henfredemars
    link
    fedilink
    English
    arrow-up
    27
    ·
    edit-2
    6 months ago

    You’re not an idiot. You’re using tools that don’t really do what they claim because it wasn’t considered an important use case.

    IPv6 is great, but we haven’t seen enough pain yet to really drive adoption on the home LAN.

    My solution uses the ISP box to deliver stateless auto conf, and bridging a consumer router. I can’t open ports but at least I get an IP.

    • Album@lemmy.ca
      link
      fedilink
      arrow-up
      5
      ·
      edit-2
      6 months ago

      Do you have an example? Because it works great on openwrt, dd-wrt, pfsense, opnsense, unifi, mikrotik…and then if you’re using the isp equipment it works out of the box.

      • henfredemars
        link
        fedilink
        English
        arrow-up
        5
        ·
        edit-2
        6 months ago

        TP-link can’t open ports in the v6 firewall neither can Linksys and it doesn’t support DHCP forward so literally was incompatible with my ISP implementation. Some current TP Link router sold at Walmart don’t even have an IPv6 firewall.

        Open source works great. Can’t speak to unifi never seen it for sale here.

      • madscience@lemmy.world
        link
        fedilink
        English
        arrow-up
        5
        ·
        6 months ago

        You’re using open source third party firmware and higher end networking gear as an example. Of course they work. Shitty consumer grade brands aren’t in the same class

          • umbrella@lemmy.ml
            link
            fedilink
            arrow-up
            2
            ·
            edit-2
            6 months ago

            tplink handles it badly ootb, youd need openwrt/ddwrt.

            my isp’s modem cant handle it well either.

            i doubt older asus/linksys/etc devices handle it well either.