[luci-app-shadowsocks-libev] Cannot disable Redir Rules
See original GitHub issueStep to reproduce
- Add an remote server and ss_redir instance. Enable redir rules. In the
Local Instances
tab, theRunning
column of the corresponding ss_redir instance saysyes
; - Check IP (e.g.
curl https://myip.ipip.net/
) to confirm the router is forwarding connections to shadowsocks server. - Check the
Disabled
checkbox in theRedir Rules
tab, then save and apply. - Back to the
Local Instances
tab, you can find that theRunning
column of the ss_redie instance still saysyes
. - Check IP and you can find that the router is still forwarding you connections.
- Edit the local instance to disable it. Save and apply.
- You can find that you lost your Internet access, which is likely because that the router is forwarding you connection to a stopped ss_redir instance.
Expected behaviour
After disabling Redir Rules, the router should stop forwarding connections.
Versions
- OpenWrt 18.06.2 r7676-cddd7b4c77
- luci-app-shadowsocks-libev git-19.034.35162-a0ae6c9-1
- shadowsocks-libev-* 3.1.3-2
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
2.2.10. Disable Source Routing Red Hat Enterprise Linux 6
It can allow a user to redirect network traffic for malicious purposes. Therefore, source-based routing should be disabled.
Read more >Understand ICMP Redirect Messages - Cisco
This document discusses packet redirect functionality provided by Internet Control Message Protocol (ICMP). ... Ethanalyzer. Disable ICMP Redirects. Summary ...
Read more >How to Disable ICMP Redirect Messages | HPE Support
This message informs a host to update its routing information and to send packets on an alternate route. There is no authentication in...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
It’s bug in the init script. Please try patching
/etc/init.d/shadowsocks-libev
like the following. It should work.Yes, it works now. Thanks!