再来发个K3梅林的koolproxy去广告的方法

校友***

首先感谢@tianbaoha @qqlikens @毛毛卷 ，前面有个帖子信息比较混乱，而且其楼主提供的包有点问题（把自己生成的证书等文件也打包在里面了）
本人也菜鸟小白一枚，经验欠缺，有问题请跟帖提出。
实现的前提是你的JFFS分区要挂载正常（挂不上的先解决挂载问题再来）
还有有的朋友说我拖进去的脚本文件不能随机启动KP，首先请查看系统设置里面有没有把这里设置成“是”
默认状态下是“否“导致你在/jffs/scripts/目录下的脚本不能随机启动。

校友***

解压我附件给的压缩包
用winscp把koolproxy文件夹拷进./jffs文件夹内
把firewall-start文件拷进/jffs/scripts文件夹内
Putty或SHELL登录后台（如果不会进后台，只会用winscp拖动文件夹，下面的命令行你不看也行，但是图还是要看的，也要照着做）
cd /jffs/scripts
chmod +x firewall-start
chmod a+rx /jffs/scripts/*

重启路由器
登录110.110.110.110下载证书导入浏览器实现去广告
为了让同样是小白的朋友看懂，配几张图

cherr***

随便看看顶一下

ssp***

虽然我懂了，但是你写的这么简单，叫那些小白熬通宵哈

luc***

小白看完要懵逼的哈哈

3435***

我问个弱智的问题，JFFS分区在哪看挂载正常不正常

校友***

343534191 发表于 2017-8-26 12:23
我问个弱智的问题，JFFS分区在哪看挂载正常不正常

对付小白，只能祭出看图说话的招了

a7718***

楼主,电视华为荣耀Pro盒子能实现去广告吗

校友***

a771853580 发表于 2017-8-26 12:41
楼主,电视华为荣耀Pro盒子能实现去广告吗

不知道哦（不用盒子的人表示）

校友***

查看路由器是否正常启动可以用shell或者putty软件登录路由器的后台，输入ps命令查看，如果发现有这样的进程，就OK了

校友***

下载证书并导入，才是去各种视频广告的前提，所以证书的下载是必要步骤。那么这个证书在哪里呢，只要启动正常，它就在路由器的某个目录下，具体请看。所以你除了进110.110.110.110（这个应该是软件映射的一个网址），还可以用winscp把证书拖到自己的电脑上，然后再导入。

fwx***

优酷视频无法播放 楼主有这个问题吗

sha***

fwx1010 发表于 2017-8-26 13:11
优酷视频无法播放 楼主有这个问题吗

优酷可以播放！！我测试的网页！！没有安装客户端！！！而且VIP一样有效

only***

能否加到梅林上呢，加个去广告，$$一般就够了，这样最方便了

一曲***

楼主 重新格式化了几次之后 JFFS按你说的查看方法可以挂载 看日志KP也应该是启动了 证书网站打不开用WINSCP安装了 就是去不了广告
有关日志如下
Aug 26 05:18:06 koolproxy[980]: koolproxy v3.6.1
Aug 26 05:18:06 koolproxy[980]: log level=4
Aug 26 05:18:06 koolproxy[980]: thread count=4
Aug 26 05:18:06 koolproxy[980]: work path=/jffs/koolproxy
Aug 26 05:18:06 koolproxy[980]: program path=/jffs/koolproxy/koolproxy
Aug 26 05:18:06 koolproxy[980]: data path=/jffs/koolproxy/data
Aug 26 05:18:06 koolproxy[980]: ttl mode=0
Aug 26 05:18:06 koolproxy[980]: mark mode=0
Aug 26 05:18:06 koolproxy[980]: max fd=131070
Aug 26 05:18:06 koolproxy[980]: init adblock engine
Aug 26 05:18:06 koolproxy[980]: load adblock normal rule: /jffs/koolproxy/data/rules/koolproxy.txt
Aug 26 13:18:07 rc_service: zcip 985:notify_rc start_firewall
Aug 26 13:18:07 dnsmasq[538]: read /etc/hosts - 5 addresses
Aug 26 13:18:07 dnsmasq[538]: using nameserver 202.97.224.68#53
Aug 26 13:18:07 dnsmasq[538]: using nameserver 202.97.224.69#53
Aug 26 13:18:07 zcip_client: configured 169.254.189.190
Aug 26 13:18:07 kernel: mtd->read(0x44 bytes from 0x29a0000) returned ECC error
Aug 26 13:18:07 kernel: Node CRC ffff34ff != calculated CRC 51dfab5b for node at 029a0000
Aug 26 13:18:07 kernel: Node CRC ffffdbff != calculated CRC 2d300f36 for node at 029a0080
Aug 26 13:18:07 kernel: mtd->read(0x44 bytes from 0x29a0000) returned ECC error
Aug 26 13:18:07 kernel: Node CRC ffff34ff != calculated CRC 51dfab5b for node at 029a0000
Aug 26 05:18:07 koolproxy[980]: load adblock daily rule: /jffs/koolproxy/data/rules/daily.txt
Aug 26 05:18:07 koolproxy[980]: WARN: load adblock daily rule failed: /jffs/koolproxy/data/rules/daily.txt
Aug 26 05:18:07 koolproxy[980]: load adblock video rule: /jffs/koolproxy/data/rules/kp.dat
Aug 26 13:18:07 kernel: mtd->read(0x44 bytes from 0x29c0000) returned ECC error
Aug 26 13:18:07 kernel: Node CRC ffffd3ff != calculated CRC bcac1b22 for node at 029c0000
Aug 26 13:18:07 kernel: Node CRC ffff11ff != calculated CRC 558d0f4e for node at 029c010c
Aug 26 13:18:07 kernel: mtd->read(0x44 bytes from 0x29c0000) returned ECC error
Aug 26 13:18:07 kernel: Node CRC ffffd3ff != calculated CRC bcac1b22 for node at 029c0000
Aug 26 13:18:07 kernel: mtd->read(0x44 bytes from 0x29c0000) returned ECC error
Aug 26 13:18:07 kernel: Node CRC ffffd3ff != calculated CRC bcac1b22 for node at 029c0000
Aug 26 05:18:07 koolproxy[980]: WARN: load adblock video rule failed: /jffs/koolproxy/data/rules/kp.dat
Aug 26 05:18:07 koolproxy[980]: load adblock user rule: /jffs/koolproxy/data/rules/user.txt
Aug 26 05:18:07 koolproxy[980]: WARN: load adblock user rule failed: /jffs/koolproxy/data/rules/user.txt
Aug 26 05:18:07 koolproxy[980]: init https engine
Aug 26 13:18:08 miniupnpd[909]: shutting down MiniUPnPd
Aug 26 13:18:08 start_nat_rules: apply the nat_rules(/tmp/nat_rules_ppp0_eth0)!
Aug 26 05:18:08 koolproxy[980]: init proxy engine
Aug 26 05:18:08 koolproxy[980]: listen socket on [0.0.0.0]:3000 success
Aug 26 13:18:08 crond[1026]: crond (busybox 1.25.1) started, log level 8
Aug 26 13:18:09 kernel: mtd->read(0x44 bytes from 0x2a20000) returned ECC error
Aug 26 13:18:09 kernel: Node CRC ffffffff != calculated CRC 0a55732e for node at 02a20000
Aug 26 13:18:09 kernel: mtd->read(0x44 bytes from 0x2a00000) returned ECC error
Aug 26 13:18:09 kernel: Node CRC ffffffff != calculated CRC 9c10e778 for node at 02a00000
Aug 26 13:18:09 kernel: Node CRC c1efffff != calculated CRC 989cc464 for node at 02a007b8
Aug 26 13:18:09 kernel: mtd->read(0x44 bytes from 0x2a20000) returned ECC error
Aug 26 13:18:09 kernel: Node CRC ffffffff != calculated CRC 0a55732e for node at 02a20000
Aug 26 13:18:09 custom_script: Running /jffs/scripts/firewall-start (args: ppp0)
Aug 26 13:18:09 miniupnpd[1062]: HTTP listening on port 38234
Aug 26 13:18:09 miniupnpd[1062]: Listening for NAT-PMP/PCP traffic on port 5351
Aug 26 13:18:09 kernel: mtd->read(0x44 bytes from 0x29c04cc) returned ECC error
Aug 26 13:18:10 kernel: Node CRC b082da74 != calculated CRC eaae440f for node at 029c04cc
Aug 26 13:18:10 kernel: mtd->read(0x44 bytes from 0x29c04cc) returned ECC error
Aug 26 13:18:10 kernel: Node CRC b082da74 != calculated CRC eaae440f for node at 029c04cc
Aug 26 13:18:10 kernel: Node CRC b082da74 != calculated CRC eaae440f for node at 029c04cc
Aug 26 13:18:19 kernel: mtd->read(0x44 bytes from 0x29c04cc) returned ECC error
Aug 26 13:18:19 kernel: Node CRC b082da74 != calculated CRC eaae440f for node at 029c04cc
Aug 26 13:18:19 kernel: mtd->read(0x44 bytes from 0x29c04cc) returned ECC error
Aug 26 13:18:19 kernel: Node CRC b082da74 != calculated CRC eaae440f for node at 029c04cc
Aug 26 05:18:19 koolproxy[980]: update detect: /jffs/koolproxy/data/rules/koolproxy.txt, online md5: 09660c95b3bc3299457eae4a3b3ab653, local md5:
Aug 26 05:18:20 koolproxy[980]: update success: /jffs/koolproxy/data/rules/koolproxy.txt
Aug 26 05:18:21 koolproxy[980]: update detect: /jffs/koolproxy/data/rules/daily.txt, online md5: fcb9c4d4a1816b5fe20782b6214414aa, local md5:
Aug 26 05:18:22 koolproxy[980]: update success: /jffs/koolproxy/data/rules/daily.txt
Aug 26 13:18:22 kernel: mtd->read(0x44 bytes from 0x29c0000) returned ECC error
Aug 26 13:18:22 kernel: Node CRC ffffd3ff != calculated CRC bcac1b22 for node at 029c0000
Aug 26 13:18:22 kernel: Node CRC ffff11ff != calculated CRC 558d0f4e for node at 029c010c
Aug 26 13:18:22 kernel: mtd->read(0x44 bytes from 0x29c0000) returned ECC error
Aug 26 13:18:22 kernel: Node CRC ffffd3ff != calculated CRC bcac1b22 for node at 029c0000
Aug 26 05:18:22 koolproxy[980]: update detect: /jffs/koolproxy/data/rules/kp.dat, online md5: edbd6d83b3247cd8ec161c2ee98885b4, local md5:
Aug 26 05:18:23 koolproxy[980]: update success: /jffs/koolproxy/data/rules/kp.dat
Aug 26 13:18:24 kernel: mtd->read(0x44 bytes from 0x2a20000) returned ECC error
Aug 26 13:18:24 kernel: Node CRC ffffffff != calculated CRC 0a55732e for node at 02a20000
Aug 26 13:18:24 kernel: mtd->read(0x44 bytes from 0x2a20000) returned ECC error
Aug 26 13:18:24 kernel: Node CRC ffffffff != calculated CRC 0a55732e for node at 02a20000
Aug 26 05:18:24 koolproxy[980]: update detect: /jffs/koolproxy/koolproxy, online md5: a175eef043eff6b9c6e961e69d980906, local md5:
Aug 26 05:18:25 koolproxy[980]: update success: /jffs/koolproxy/koolproxy
Aug 26 05:18:25 koolproxy[980]: reboot by program update
Aug 26 13:18:26 kernel: mtd->read(0x44 bytes from 0x2940000) returned ECC error
Aug 26 13:18:26 kernel: Node CRC ffffffff != calculated CRC 97ab944d for node at 02940000
Aug 26 13:18:26 kernel: Node CRC ff79ffff != calculated CRC f3167930 for node at 029406e0
Aug 26 13:18:26 kernel: mtd->read(0x44 bytes from 0x2920000) returned ECC error
Aug 26 13:18:26 kernel: Node CRC ffffffff != calculated CRC 1e6601e7 for node at 02920000
Aug 26 13:18:26 kernel: mtd->read(0x44 bytes from 0x2940000) returned ECC error
Aug 26 13:18:26 kernel: Node CRC ffffffff != calculated CRC 97ab944d for node at 02940000
Aug 26 13:23:03 dropbear[1535]: Child connection from 192.168.1.206:49157
Aug 26 13:23:04 dropbear[1535]: Password auth succeeded for 'admin' from 192.168.1.206:49157
Aug 26 13:23:47 dropbear[1535]: Exit (admin): Exited normally
Aug 26 13:25:13 dropbear[1798]: Child connection from 192.168.1.206:49460
Aug 26 13:25:41 dropbear[1798]: Login attempt for nonexistent user from 192.168.1.206:49460
Aug 26 13:25:46 dropbear[1798]: Login attempt for nonexistent user from 192.168.1.206:49460
Aug 26 13:25:52 dropbear[1798]: Login attempt for nonexistent user from 192.168.1.206:49460
Aug 26 13:25:59 dropbear[1798]: Exit before auth: Exited normally
Aug 26 13:26:05 dropbear[1865]: Child connection from 192.168.1.206:49533
Aug 26 13:26:09 dropbear[1865]: Password auth succeeded for 'admin' from 192.168.1.206:49533
Aug 26 13:26:35 dropbear[1865]: Exit (admin): Exited normally