Wireguard performance on AR-300M with Lede

Will this bug be fixed in the new GUI ?

I understand why people are frustrated & confused: there are also conflicting directives between the instructions found on GL.inet, Wireguard.com (for OpenWRT), and various VPN web proxy services, for example:

# opkg install wireguard

# opkg install kmod-wireguard
https://docs.gl-inet.com/

→ What is the difference between “wireguard” & “kmod-wireguard” ?

Where commercial VPN services attempt to automate WireGuard installation using a shell script, the script fails on GL.inet firmware because curl is not installed. After installation of curl, the script fails because ca-bundle is missing:

curl: (77) Error reading ca cert file /etc/ssl/certs/ca-certificates.crt - mbedTLS: (-0x3E00) PK - Read/write of file failed

I understand that some people here are using WireGuard in applications where they control both ends of the tunnel. But GL.inet firmware should also support WireGuard with commercial VPN proxy services. This means:

  1. Published installation scripts for OpenWRT should complete without errors
  2. Published instructions for the OpenWRT LuCI GUI should work properly on GL.inet firmware

REFERENCES

https://danrl.com/blog/2017/luci-proto-wireguard/

1 Like