It is only a beta version where Wiregurd does not work as an example. It has also been tested extensively
WireGuard works fine on op24. I am using it all day long.
2 Likes
I tested 3 different providers.
Either via Config File or Manually not one of them is started.
Then there must be an issue and you should post your logs and configs.
I can just say that I am using Mullvad all day and it works as fine as always.
4 Likes
Now it's pretty simple.
I take version 4.6.2 Clean Install and test Wireguard. Every provider runs. WiFi just cuts out regularly for unexplained reasons.
I noticed with 4.6.2 that he prefers it when no USB drive is connected and WLAN 2.4 is not set to AX.
If I install version 24 even clean install, Wireguard doesn't start at all.
Please create a new thread about it, posting all logs.
As said before op24 works totally fine for me, even using wg.
3 Likes
Yes, there is a problem with the interferance on the 2.4GHz and GL-iNet reproduced the problem.
I believe this will not be fixed:
You doing something wrong then, because I'm being using wireguard as a client and as a server all day long for over 2 months on "op24"
2 Likes
What can you do wrong with a clean install???
24 Install. Then import one of the 3 different Wireguard Config files and you're done.
If I do this with 4.6.2 in the same procedure, wireguard works immediately.
The difference is only the firmware.
Well not much, but that does not explain to us what other things you have configurated, or how the topology or use of setup is 
Last time i had a discussion with someone about internet cables, he said it were not his cables because someone did it for him, but when i looked to them the cable core was shown outside of the shielding, he thought it was supposed to be like that.
just like that 2 people have a different view on something and not visible if you don't know it, but things like this is still very relevant information 
2 Likes
Maybe try downloading the op24 firmware again, and to really make sure, check the checksum after downloading and flash it through u-boot. I agree with others, op24 works with WireGuard.
1 Like
I have set up a WireGuard client on my Flint 2 (4.6.2) and the server is under a dynamic dns (duckdns domain). Although I have set up the watchdog cron job on my flint, if the server changes an ip address then WireGuard does not reconnect.
Any idea how to fix this?
WireGuard won't reconnect automatically because it does not really know if a connection fails.
So your watchdog should disable VPN, clear DNS cache and enable VPN again.
Hi @admon
I am using the /usr/bin/wireguard_watchdog script, added in /etc/crontabs/root like this:
* * * * * /usr/bin/wireguard_watchdog
But every time the ip changes on the server, it need to manually disconnect and reconnect the client.
I never heard of this script. Where does it come from?
It's part of Wireguard-tools and already installed on Flint 2. Here is the commit message @ openwrt
I have found that for people it worked (topic @glinet forum) but it doesn't seem to do the job for me.
Totally random question: If I load a backup (created using LuCI) into a clean install (without keeping settings), will the result be exactly the same as if I had kept the settings?
Yes and no.
Only config files will be kept, so installed opkg packages will be either reinstalled or missing.
I meant: Many people here suggest not upgrading with the "Keep settings" option ticked, claiming this is a much safer and error-free process.
But if I restore from a backup, will the result be the same as keeping the settings? So, is there actually any advantage to not keeping the settings and instead restoring from a backup?
Often it takes from full /etc/ but only config files however this is not always the case, what you get from the backup feature is also what you keep if you upgrade with keeping the settings.
In rare situations some files doesn't get recognized to be backed up, i think ive seen this on /etc/avahi but then you can add them inside the /etc/sysupgrade.conf
It however does not take other things, like functions or scripts, i think it more than often only track it by files with certain extensions.
Edit:
Also one reason why one unticks the preserving, is because sometimes there are namings declared of devices in the configs, which may are changed due to driver changes, this is one example why MTK -> OP24 or OP24 -> MTK always need to have this unticked, it can result in issues, maybe even boot issues because it crashes on loading the wireless config.
^ though this example is not a good example, mtk and op24 are too different maybe also on the update mechanism so u-boot is recommended just pointing this out because otherwise people might mis interpret my example 
, but the idea is the same.
1 Like