I’ve gone through this process a few times over the last week since trying out WireGuard, and for the most part it’s been seemless. There’s hiccups here or there, but normally just me misconfiguring my keys/ config file.

Typically on the client (my phone, tablet, etc) there is an option to generate the key pairs. I’ll then put the public one on my peer definition in pfsense, and away we go.

With this GL.iNet router however, there is no option (that I see) to generate the key pairs… so I think the problem I’m running into is that they are not matching/ expected when the negotiation with my firewall happens.

How can I go about generating these keypairs? Has anyone had this issue with GL.iNet?

EDIT: After finding a post from GL.iNet staff advising to not have a Listening port in the Peer section, and to set the MTU to around 1300, I have everything working as expected.

  • adONis@lemmy.world
    2·
    9 months ago

    I’m not familiar with the GL, but I’ve configured some WG connections (purevpn) on my opnsense, and I recall using echo privatekey | wg pubkey to generate a public key from a private key for WG.

    I hope this helps somehow.