Please read FAQ then answer these questions before submitting your issue. Thanks!
_Put an x inside the [ ] that applies._
在自定义规则里面,建议加入继续'某项规则',例如基于GFW List,然后在这上面再添加自定义。现在的自定义是直接导入了GFW List吧,这样的话要是GFW List更新了,但是导入的规则很难对比出修改了什么,这样就不太好了
感觉纯粹基于某规则也并不是完全适合。
现有acl导入只能bypass,功能实在太弱了。
The best way to propose new features is opening a pull request.
看起来在咱的建议上添加可以基于现有所有规则就可以满足汝的要求了,而想调整gfwlist的人就直接导入就好了,想使用最新gfwlist的同时又想添加自己规则的就使用'基于gfwlist'这样就好了
Simon Shi notifications@github.com于2017年6月6日周二 10:41写道:
感觉纯粹基于某规则也并不是完全适合。
- 选择基础模式
让用户选择[proxy_all]或者[bypass_all],以适应不同需求- 调整[bypass_list]
这里可以加入lan,China ip这种预留类型,用户自行修改- 调整[proxy_list]
这里可以加入gfwlist,China ip这种预留类型,用户自行修改- custom acl backup
导出到本地或者导出到Google drive现有acl导入只能bypass,功能实在太弱了。
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/shadowsocks/shadowsocks-android/issues/1276#issuecomment-306365621,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJoPKTbvLjH6TXAwIIcbig3B2A36MgF-ks5sBLxCgaJpZM4NwvnS
.
Implemented in 4.2.0. Will be released soon.
I tried this one.
https://github.com/shadowsocks/shadowsocks-libev/raw/master/acl/chn.acl
But there is no response after I clicked the button. Nothing is on my screen.
Although I known the acl has been imported by finding files in data partition under the help of superuser, I am still confused with it for its "different but looks same" …
试了下,直接把https://raw.githubusercontent.com/ACL4SSR/ACL4SSR/master/fullgfwlist.acl 链接地址放到规则里就行了。
好用。
acl规则怎么使用?在自定义规则那里直接添加然后写acl地址吗?
对的 自定义规则-手动设置-URL/blahblah
huaxianyan notifications@github.com于2017年8月7日周一 23:08写道:
acl规则怎么使用?在自定义规则那里直接添加然后写acl地址吗?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/shadowsocks/shadowsocks-android/issues/1276#issuecomment-320690406,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJEkg3NYn22Znrao5NCsrCQTTBoSPBjAks5sVyh7gaJpZM4NwvnS
.
@simonsmh 添加完就是本身的URL吗?我以为会把里面的内容读取出来写进规则
Most helpful comment
Implemented in 4.2.0. Will be released soon.