问题3还是关于原来的备份的配置文件的问题
把备份文件拷入后无法在原有组策略里添加策略提示
polgrp_add_policy: cannot open /usr/panabit/etc/polgrp_4.conf: no such file
原帖由 Lucifer 于 2007-8-9 13:05 发表 http://www.panabit.com/forum/images/common/back.gif
问题3还是关于原来的备份的配置文件的问题
把备份文件拷入后无法在原有组策略里添加策略提示
polgrp_add_policy: cannot open /usr/panabit/etc/polgrp_4.conf: no such file
原有的策略文件不能再用。
原帖由 panabit 于 2007-8-9 13:05 发表 http://www.panabit.com/forum/images/common/back.gif
如果是阻断，单IP限速就不会产生效果，你填0就可以了。
哦。感觉是UI设计的问题用户体验很不好。我修改界面的话可以吗？我想优化一下用户体验。
原帖由 panabit 于 2007-8-9 13:06 发表 http://www.panabit.com/forum/images/common/back.gif
原有的策略文件不能再用。
ok我删除掉重新部署
原帖由 Lucifer 于 2007-8-9 13:07 发表 http://www.panabit.com/forum/images/common/back.gif
哦。感觉是UI设计的问题用户体验很不好。我修改界面的话可以吗？我想优化一下用户体验。
可以，如果你改完了，给我们share一下可好？
原帖由 panabit 于 2007-8-9 13:20 发表 http://www.panabit.com/forum/images/common/back.gif
可以，如果你改完了，给我们share一下可好？
当然。
问题3
策略计划里右上角还是有数据通道的选项。点击后还是可以进入。。。。。。。。。。
问题4我把所有的策略组删除后点击应用提示成功后当前策略还是显示为空策略
策略无法生效。我考虑彻底删除重新安装。
原帖由 Lucifer 于 2007-8-9 13:30 发表 http://www.panabit.com/forum/images/common/back.gif
当然。
问题3
策略计划里右上角还是有数据通道的选项。点击后还是可以进入。。。。。。。。。。
这个我们疏忽了，谢谢！
啊策略没有应用是我把时间搞错了=。=抱歉
问题5
…………FTP的没了又变成电驴了。。。。。。。
get edonkey node 61.172.205.9:7010
get edonkey node 202.108.0.103:443
get skype node 222.28.155.37:443
get edonkey node 222.141.221.180:443
get edonkey node 211.154.165.35:443
get edonkey node 61.183.254.114:7010
get edonkey node 222.141.221.199:7010
get edonkey node 202.108.0.103:443
get edonkey node 62.241.53.17:443
62.241.53.17:443 is a server emule node
get edonkey node 221.234.143.206:6648
221.234.143.206:6648 is a client emule node
get edonkey node 58.252.202.2:6252
58.252.202.2:6252 is a client emule node
get edonkey node 221.220.68.115:7558
get edonkey node 61.48.223.76:6251
get edonkey node 58.69.12.114:6250
get edonkey node 124.135.80.125:7558
58.69.12.114:6250 is a client emule node
221.220.68.115:7558 is a client emule node
get edonkey node 80.161.29.108:5147
get edonkey node 125.115.34.219:6251
61.48.223.76:6251 is a client emule node
125.115.34.219:6251 is a client emule node
80.161.29.108:5147 is a client emule node
124.135.80.125:7558 is a client emule node
get edonkey node 125.119.232.158:6256
get edonkey node 60.208.225.17:7552
60.208.225.17:7552 is a client emule node
125.119.232.158:6256 is a client emule node
get edonkey node 58.49.26.108:4662
get edonkey node 218.17.63.197:4662
58.49.26.108:4662 is a client emule node
218.17.63.197:4662 is a client emule node
get edonkey node 221.237.112.242:7559
221.237.112.242:7559 is a client emule node
get edonkey node 58.48.169.211:51634
58.48.169.211:51634 is a client emule node
get edonkey node 61.48.123.206:10700
61.48.123.206:10700 is a client emule node
get edonkey node 219.153.141.132:5616
get skype node 219.153.141.132:5616
219.153.141.132:5616 is a client emule node
get edonkey node 61.172.205.8:7010
get edonkey node 61.183.254.53:443
get edonkey node 221.169.231.146:6646
221.169.231.146:6646 is a client emule node
get edonkey node 222.93.165.228:4161
222.93.165.228:4161 is a client emule node
get edonkey node 62.241.53.17:443
62.241.53.17:443 is a server emule node
get edonkey node 61.48.223.76:6251
61.48.223.76:6251 is a client emule node
get edonkey node 61.172.205.9:7010
get edonkey node 202.108.0.103:443