Synology DSM - nftables not supported #52
Comments
|
You seem to be using Synology. The error message is a little different but this might be related to: #50. Could you please add |
|
Its running for almost a year on my Synology. Here log output: |
|
Maybe its was nothing. But after I started the container with the extra lines etc. It seems my whole network get unstable.... |
|
Can you try loading the module manually on your host (synology) using |
|
Nothing... |
|
Yeah it seems like the Synology DSM Kernel isn't built with nftables support enabled. I didn't expect to come across any up-to-date systems without nftables support as it is supported since kernel version 3.13 and has been slowly replacing iptables-legacy since then. For now, please use the old image Once I got a little more time, I'll see how to deal with that. I'd rather not switch back to iptables, but I might be left with no choice if I wanna support Synology. I am open to suggestions btw |
|
Revert back to |
Trigus42
changed the title
Which one is newer?
I'm sorry but I can't figure it out by myself |
|
Just letting everyone know, this doesn't only affect a Synology NAS. I ran into the same issue on a Tinkerboard S running Tinker OS. The "trigus42/qbittorrentvpn:7871e66f8529db34ac58b54e1df56d9db51cf2e5" image fixed the issue for me, but I'm guessing it can never be updated from there? |
|
I have created a |
|
legacy-iptables didn't work for me. It looked like the vpn would connect, but errors adding rules, though I don't have the output. Had to go back to 7871e66 which still works for me. |
|
I believe I'm having a related issue, running on QNAP's Container Station (which has its own issues but not related to this) and like @krazeedrivr On Jun 1, trigus42/qbittorrentvpn:7871e66f8529db34ac58b54e1df56d9db51cf2e5 does fix it my QNAP host indeed does not have nf_tables support, but the :latest image & LEGACY_IPTABLES=yes does not seem to fix it. I found a post somewhere about something else vaguely related with folks complaining about QNAP/Synology's setup suggesting forcing iptables version 1.6 and nothing later. I am at the limit of my knowledgeability to help, but I would be happy to schedule a time where we could interact directly say on discord and I could screenshare/we could run some commands together and try and troubleshoot for everyone? If you're interested, DM me on discord which I am a lot more likely to see notifications from (my discord username is uintXX_t except replace XX with the common full integer width all modern architectures use these days) otherwise feel free to disregard! Thank you for your work putting this together |
That's interesting. I have build a new image |
Didn't use qBittorrent for some days but its was not reachable. Saw some errors. App is working with VPN off. But with VPN on I get the errors see below the compose information:
Debug log information
The text was updated successfully, but these errors were encountered: