Posted: Fri Jul 31, 2020 12:39 Post subject: ALGO VPN X EC2 X DD-WRT Wireguard
Hi there.
This is my first post and first of all TKS A LOT for all the information hanging around.
I dont have much (or any) knowledge about networking but after a week of research i finally build an AWS EC2 instance using ALGO VPN.
From the beginning i was kind of worried but worked like a magic and know i have an AWS instance running as a VPN server and Algo already generated the clients files configuration for me.
Thats the problem.
On my macbook i am using wireguard and it was easy. Just config import.
Same for IOS. Just a qrcode scanning.
BUT, when i try to create a tunnel in the router, i go to the tunnels sections, select WIREGUARD, but the LOCAL PUBLIC KEY is already filled by default. Theres no way to cut it and paste my own code (wich ALGO generate for me)
I assume that the iNTERFACE PRIVATE in the client config file is the LOCAL PUBLIC key in the router.
Am i right? I am attaching the config file view and my router view.
Joined: 04 Aug 2018 Posts: 1447 Location: Appalachian mountains, USA
Posted: Fri Jul 31, 2020 15:22 Post subject:
The Local Public Key is created automatically from the Local Private Key. _________________ 2x Netgear XR500 and 3x Linksys WRT1900ACSv2 on 53544: VLANs, VAPs, NAS, station mode, OpenVPN client (AirVPN), wireguard server (AirVPN port forward) and clients (AzireVPN, AirVPN, private), 3 DNSCrypt providers via VPN.
(which will tell you to always state router model and build number and not to use the router database)
You are using an old build that is for sure newer builds can alter keys and much more.
See my signature at the bottom for necessary documentation about wireguard
Hi all. Tks for the input.
My router is an asus rt 3200 and yes i was using an old firmware.
I updated it and know its running Firmware: DD-WRT v3.0-r43904 std (07/23/20)
After the update i received a handshake. But no data in as the attached. transfer: 0 B received, 6.21 KiB sent
I read and download the guide from your signature. About the changeset 43029 ..do i need it since my version is 43904?
If the answer is yes, i dont a have a clue how to do it. I see green and red lines. I suppose that the green lines should replace the red ones... do i have to copy/paste and run at the command shell? Should i edit mannualy?
Joined: 18 Mar 2014 Posts: 12915 Location: Netherlands
Posted: Sat Aug 01, 2020 6:35 Post subject:
See page 17 of the ddwrt wireguard server setup guide
MTU size problems (Connection, but no traffic, hang, slow loading, or no streaming media)
MTU problems often manifest themselves as connections which hang during periods of active usage, or does
not load the whole page when browsing. Or you can connect but not see or use streaming media (like an IP
Camera) or your connection is unexpected slow.
The MTU (Maximum Transmission Units) is the maximum datagram size in bytes that can be sent
unfragmented over a particular network path. Wireguard requires that packets be sent unfragmented.
MTU size is set in the GUI and is standard 1460 for IPv4 and 1420 for IPv6. But sometimes this is too high
especially if you are using connection via LTE.
You can try lowering the MTU with trial and error i.e. start at 1024 (for IPv6 the minimum MTU is 1280) and
work your way up or use the approach describe at: https://www.sonassi.com/help/troubleshooting/setting-correct-mtu-for-openvpn
Make sure to reboot the router after changing!
