Looking for feedback on Wireguard capable wifi routers that keep a persistent link from the router to an endpoint. A lot of what I see advertised as “Wireguard Supported” sets up a server and not a client.

The GL.iNET routers seem to do it, anyone with experience with these? https://docs.gl-inet.com/router/en/4/interface_guide/wireguard_client/

Bonus for being able to push a wireguard client config to the device via API/cli.

  • litchralee@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    1
    ·
    30 days ago

    I have a GL.iNET 4G router that I’ve configured WG for, and it worked exactly as expected. In my case, I had a requirement that when roaming onto a new tower, the tunnel had to recover automatically. And it seemingly did. Even though the router itself was mostly stationary, the mobile carrier’s CGNAT endpoint would change and the router gracefully adapted to that

    I would have preferred to use IPv6 – which the router also supports, but off by default – to avoid CGNAT but the opposite end of the WG tunnel had complexities which precluded that.

    • uenticx@lemmy.worldOP
      link
      fedilink
      English
      arrow-up
      2
      ·
      30 days ago

      Was there a noticeable disruption between towers? It’s taking resolvd a good 10 seconds to catch up when turning the client on and off. Maybe I should disable cache all-together.

      • litchralee@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        0
        ·
        30 days ago

        Alas, I never witnessed the handover happening live, only that my logs from the far end of the tunnel would show that tunnel uptime had reset.

        I imagine there’s a tunable parameter to adjust the WG keep alive, which could help reduce the drop time.