When ss-redir is used, only incoming traffic is redirected (chain PREROUTING).Workaround is possible by recompiling the missing modules and iptables. DSM does not include the needed kernel modules for TProxy (at least on my model), which prevents using ss-redir with udp.Graphical interface does not allow to view the logs.Use SSH and edit json files manually if any issue. Graphical interface is still experimental: it works well on my model but might not on others.If not working, just drop the v2ray-plugin executable into /var/packages/shadowsocks-libev/target/bin (and tell me what works for you). Not really sure which one goes into which architecture so probably not working for all.
I don't know how to compile v2ray-plugin using Synology's dev environment so I just copy the binaries provided in the project.Branch dsm6 works on DSM 6.1 and 6.2 (not maintained anymore).This is needed for DSM to show the shadowsocks config app in the app list. Service is considered "started" in DSM even though no shadowsocks service could be started.I had a hard time with the migration to DSM7 so things might still have bugs.
Since DSM7, after installing the package, it is needed to manually ssh into the Synology and run: sudo /var/packages/shadowsocks-libev/scripts/addprivileges.Since 3.3.5, being the default admin user is not needed anymore. The user installing the package must have admin rights.udp will/might not work (see limitation below). The incoming non-local traffic will be routed to ss-redir through iptables. If ss-redir is used, then routing will be activated. When removing the package, the config files are kept and reused if the package is reinstalled. Names must be: ss-local.json ss-tunnel.json ss-redir.json ss-server.json ss-manager.jsonĪdditional instances can be created with names: ss-local-xxx.json ss-tunnel-xxx.json etc. Note: configuration file(s) are stored into /var/packages/shadowsocks-libev/etc. Services will restart automatically in case of reboot or restart from the Package Center. UsageĪfter installing the package, create configuration files and start the service(s). See architectures on Synology knowledge base.
Graphical interface to set-up the configuration files and start/stop the service(s) (experimental).ĭownload the spk for your architecture from the Release section, then install using Synology Package Center button Manual Install. Synology DSM packages for Shadowsocks-libev, with v2ray plugin.