4/25/2023 0 Comments Shadowsocks libevThis 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.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.Synosystemctl start stop -type=service 'pkg-ss-* ' You can check / control them in the SSH shell (as root) with commands such as: 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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |