-
Notifications
You must be signed in to change notification settings - Fork 134
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not working with DSM 7.1.1-42962 Update 1 #168
Comments
Hello, I have DS 220j with upgrade Compiled manually with params Installed as mentioned in the guide, everything works fine for me. |
@Lodifice I also ran into this problem with 7.1.1-42962, on a DS418. As far as I can tell, there's something buggy with the resulting |
@sergey-brutsky Thanks for your answer, but you're running an older version of DSM than I. With your version, I didn't have problems either. Also check your @zeldovich it's good to know I'm not the only one with that problem, thanks for opening the issue. |
You right, my DSM_VER is 7.1, but I've compiled wireguard against DSM_VER 7.0 because it didn't compile for 7.1 |
Same problem with |
Hi, guys same problem on |
Seems like wireguard kernel module does not work for 7.1.1. No idea about the root cause, but segfaults and system crashes are too scary to continue investigation. Fortunately, NAS is restarting by itself and getting back to life after some time. As a proof of concept I was able to connect via user-space client https://github.com/WireGuard/wireguard-go |
Working well for me on 918+ with both 7.1.1 Update 1 and 7.1.1 Update 2. |
How did you compile your version then? |
We used a workflow for Github actions: https://github.com/vegardit/synology-wireguard/blob/master/.github/workflows/build.yml |
Amazing! let me try that Did you try on DSM 7.1.1-42962 Update 2 ? |
Yes, the module loads successfully. Haven't tried to bring up a tunnel yet. Did it work for you? |
It seems to work well, at least for accessing my local network with it. thank a lot for the effort |
New URL: https://github.com/vegardit/synology-wireguard/releases |
Same story for me |
It doesn't work for me too. The system doesn't respond anymore and I have to shut it down manually. |
On DS220j with DSM 7.1.1-42962 Update 2 its not working, when WireGuard starts, NAS stops responding, automatic reboot.. DS220+ and DS920+ (DSM 7.1.1-42962 Update 2) it works perfectly I think all NAS higher than DSM 7.0.1-42218 Update 5 with Realtek RTD1296 SoC have the problem |
Same issue on DS720+ with DSM 7.1.1-42962 Update 2, |
Have you solved your problem yet? My version is DS920+ with DSM 7.1.1-42962 Update 2. When I run the "wg-quick up wg0", the system also crashes. here are the error reports |
Just wondering if anyone managed to solve this issue? Synology DS218 |
@AlexeyGG, I couldn't find a solution to this issue, but I managed to find a workaround by using the userspace version of WireGuard Here are the steps to follow:
This workaround is a bit clumsy, but I can try to publish a fork in the next couple of days to simplify the process. |
That would be great if you could. Going to give this a go since I've had to put something in front of one of my offsite backups in the interim hoping for some kind of fix. |
Hi, I have a DS 220j and with the recent upgrade to 7.1.1-42962 Update 1, WireGuard stopped working. I rebuilt the package and installed it again, but without success.
The intended (and previously working) use case is a VPN client inside a home network (behind NAT) that connects to a server running WireGuard. When I tcpdump on the server, I can see packets coming from the client and responses going out, but according to the WireGuard logs, the handshake never completes. It's strange that the port number of the client's endpoint entry is reported as 0 (which is not a valid UDP port). When I tcpdump on the client, I can see ICMP messages that the packets to the invalid UDP port 0 are dropped (these are the server responses, apparently) and the RX counter of
wg show
stays at zero.Moreover, once setup the wg0 interface cannot be brought down, as
ip link del dev wg0
segfaults. Then the entire system slowly becomes unresponsive and a forced shutdown is the only option.Has anyone experienced a similar issue? Or can someone give some pointers on where to dig further?
The text was updated successfully, but these errors were encountered: