Wireguard way slower than expected on AX1800 Flint

caesarsalad · 2022-12-14T12:21:20.331Z

Not a frustrating suggestion at all. This is currently a secondary router I want to be my main. But I should mention, I’ve already done this 3 or 4 times. I even completely deleted my cloud vps and reinstalled everything, got new configurations, uploaded that to the router multiple times. I just have no idea.

I suppose I’ll try to downgrade with Uboot, although not looking forward to it, I just bricked a TP-Link a week ago using TFTP.

jdub · 2022-12-14T12:24:15.651Z

Depending on your desire to use the actual GL.iNet firmware, you might also consider trying a more stock OpenWrt build, which can be made from the gl-infra-builder. I’ve found it to be considerably more stable on my AXT1800 than the stock firmware. Happy to help you through building or send you a build privately if you’re interested.

caesarsalad · 2022-12-14T12:27:35.147Z

This post would’ve been an essay if I included all the context. I’ve been through a nightmare in the past 2 weeks trying to get any Wireguard VPN working on any router. I’ve tried a Raspberry Pi 4b with OpenWRT and RaspAP. Didn’t work. I tried a TP-Link Aracher A7, didn’t work and I bricked the router. So now here I am with the flint.

I’ve honestly been through hell trying to fully figure out OpenWRT that I didn’t even want to spend the money on the flint, but for the simplicity, it was supposed to be worth it. Unless I have extermely straightforward directions, I’m not super confident about that. I’m just slightly irritated that it’s very, very close to working on stock, but just won’t.

jdub · 2022-12-14T12:50:26.830Z

Have you considered trying OpenVPN? With reasonable settings, it’s not too hard to get 160 plus megabits on that hardware.

If you already have the server set up, I don’t mind showing step by step directions for stock OpenWRT. Depending on your use case, the upcoming Tailscale update might also be worth looking into, though. I suspect you’ll only get about 100 megabits there based on my current testing.

caesarsalad · 2022-12-14T12:59:06.421Z

This would feel like a waste of money if it were just OpenVPN, could’ve just bought some cheap used tp-link and ran it like that. I don’t want to compromise a ton of my network.

I downgraded back to version 3. Same results, like 40/40. Again runs flawlessly on my phone, same config. Ugh.

I appreciate the suggestions but I’m feeling pretty defeated, 2 weeks straight of this is mind-numbing for me. All just to put a VPN on a router.

Edit: Speedtest CLI ran. Same results. Great.

Edit 2: I literally have the wireguard VPN installed on the router. If I run a speed test on my phone (connected on 5ghz) the speeds are terrible. But if I run Cloudflare Warp on my phone (so now a double-vpn) then the speeds are faster than if warp is off? What? I’m just mindblown at this point.

jdub · 2022-12-14T13:08:10.466Z

Again, are you running speedtest-cli on the router or are you running it on your computer?

People poopoo ovpn, but with the new routers that have cortex53’s, you can get performance that is on par with WG from older armv7 solutions. I doubt you’ll find a cheap TP-Link that will do 180mbps up/down on OpenVPN. But anyway.

Can you post your config file with keys redacted?

caesarsalad · 2022-12-14T13:20:44.539Z

You want me to SSH into the router and run it like that? Never done that, didn’t think that could be done.

Just redact the keys? Everything else is safe?

jdub · 2022-12-14T13:22:32.629Z

Yes, ssh into router, download / install speedtest (armhf) from link I sent way back, ungzip, run. The point is to answer whether the problem is the link itself or some sort of firewalling/NAT/something else.

I’d redact the endpoint IP too, but everything else is ok.

caesarsalad · 2022-12-14T13:23:33.063Z

Alright, I’ll try that. In the meantime…

[Interface]

PrivateKey = xxx

Address = 10.49.0.2

DNS = 172.21.63.94

[Peer]

PublicKey = xxx

PresharedKey = xxx

AllowedIPs = 0.0.0.0/0,::/0

Endpoint = xxx

jdub · 2022-12-14T13:27:19.515Z

Take out the DNS to see if that makes a difference, and add a /32 on the end of your address.

e.g. my current config:

[Interface]
Address = 10.75.50.50/32
ListenPort = 5320
PrivateKey = PK

[Peer]
AllowedIPs = 0.0.0.0/0
Endpoint = w.x.y.z:1234
PersistentKeepalive = 25
PublicKey = PK
PresharedKey = PK

caesarsalad · 2022-12-14T13:30:46.324Z

I actually sent the wrong config, but regardless I made those changes. Maybe a coincidence but it lowered ping by a little and now the download goes around 100 - 130. Still not great but better.

jdub · 2022-12-14T13:32:23.140Z

What is your output from

wg show

on the router? Basically, do we actually know that traffic is going through the tunnel?

(redact keys and endpoint)

caesarsalad · 2022-12-14T13:33:18.438Z

interface: wg0
public key: xxx
private key: xxx
listening port: 59585

peer: xxx
preshared key: xxx
endpoint: xxx
allowed ips: 0.0.0.0/0
latest handshake: 6 seconds ago
transfer: 789.91 MiB received, 85.33 MiB sent
persistent keepalive: every 25 seconds

jdub · 2022-12-14T13:35:34.242Z

Ok, that looks fine. If you run top on the router while a speedtest is running, what does the “idle” number at the top do?

alzhao · 2022-12-15T04:47:08.660Z

One parameter to manipulate is the mtu of wireguard interface.

You can find it in in UI. Try value between 1280 to 1380.

wgadm · 2024-05-27T13:07:11.299Z

Dea valued users.
I have the same problem with my Flint 2.

My Flint 2 is the WG Server and my ISP ADSL speed is 100 Mbits
My iPhone is the WG Client. Without active WG connection I've a speed with LTE 240 Mbits, with active WG connection 12 Mbits.

I've tried all of the solutions what you all recommended, but its not working.

Here my WG Client Config file details:

[Interface]
Address = 10.2.0.2/24
PrivateKey = blablablablablaE224=
DNS = 192.168.2.1 (I've tried every known DNS services. The DNS filed in the WG app is required)
MTU = 1400

[Peer]
AllowedIPs = 0.0.0.0/0,::/0
Endpoint = xyzxyzxyzxyz.glddns.com:5320
PersistentKeepalive = 25
PublicKey = blablablablablaA5646546484=

admon · 2024-05-27T13:08:29.692Z

12 Mbps is totally fine for 100 Mbps ADSL.
ADSL (a = asymmetric) means that your upload is waaaay slower than your download.

ADSL with 100 Mbps down will mostly have 10–20 Mbps up.
Since all your traffic from client will rout through your ADSL router first, the upload speed of your ISP will cap it.

wgadm · 2024-05-27T13:11:02.472Z

Ohhh noooo. Bad news. I hate my ISP.

But a question in addition: Is it same with Fiberglass connections?

admon · 2024-05-27T13:14:14.545Z

wgadm:

Is it same with Fiberglass connections?

Mostly not, but depends on your ISP and the contract.

wgadm · 2024-05-27T13:18:28.066Z

I did take a look on my contract. Its not a ADSL it is VDSL. Is there something different?