Veldkornet
Senior Member
Looks like spclient.wg.spotify.com was the one that was needed. After adding it and removing the certificate that was generated earlier, it seems to be working now.
Sent from my iPhone using Tapatalk
ublockr - a minimalists approach to adblocking
- Thread starter swetoast
- Start date
- Status
Looks like spclient.wg.spotify.com was the one that was needed. After adding it and removing the certificate that was generated earlier, it seems to be working now.
Sent from my iPhone using Tapatalk
swetoast
Guest
yepp basicially
it will post in the syslog of the router and yes it will block https ads
http://<yourrouterip>/servstats will show what it blocks
it will post in the syslog of the router and yes it will block https ads
http://<yourrouterip>/servstats will show what it blocks
well i have https+1810, but https://192.168.2.1:1810/servstats gives 404.
Gesendet von meinem SM-T810 mit Tapatalk
Gesendet von meinem SM-T810 mit Tapatalk
swetoast
Guest
Run pixelserv at port 80 and 443 to block ads
And to add more sources check ip.list or no.ip depending on if the source has a ip infront of the DNS and the other is just add the DNS you want to whitelist into the whitelist.filter
swetoast
Guest
If you installed it from repo then no else yes
If you want support for pixelserv there is a excellent thread here on the forum
Hmm, i dont understand. i installed it via opkg install pixelserv-tls.
My question is if your script starts pixelserv-tls automatically as i dont see it in the task list. Do i need to add this line to some autostart script ? My services-start actually look like this:
cru a ublockr "0 0 * * * /opt/bin/ublockr"
pixelserv-tls 192.168.2.1 -p 80 -k 443 -u admin
RC='/opt/etc/init.d/rc.unslung'
i=30
until [ -x "$RC" ] ; do
i=$(($i-1))
if [ "$i" -lt 1 ] ; then
logger "Could not start Entware"
exit
fi
sleep 1
done
$RC start
After some time of surfing my servstats look like this:
pixelserv-tls version: V35.HZ12.Kh compiled: Jul 20 2016 22:57:01 options:
uts: Uptime 0 days 02:13
req: Total # of requests 2949
avg: Avg size of reqs 738 bytes
rmx: Max size of reqs 3623 bytes
tav: Avg process time 109 ms
tmx: Max process time 10003 ms
err: # of error reqs 0
tmo: # of client timeout 8
cls: # of client shutdown 2288
nou: # of reqs w/o URL 0
pth: # of invalid URL 0
nfe: # of missing file ext 144
ufe: # of unknown file ext 17
gif: # of GIF reqs 37
bad: # of unknown HTTP methods 0
txt: # of TXT reqs 266
jpg: # of JPG reqs 2
png: # of PNG reqs 8
swf: # of SWF reqs 0
ico: # of ICO reqs 10
slh: # of HTTPS /w a good cert 0
slm: # of HTTPS w/o a cert 2110
sle: # of HTTPS /w a bad cert 0
slu: # of unrecognized HTTPS 156
sta: # of HTML stats 11
stt: # of text stats 0
204: # of HTTP/204 (no content) 0
rdr: # of redirects 70
pst: # of POST method 17
hed: # of HEAD method 0
log: access log enabled (0=no 1=yes) 0
@IngoPan, since you're running pixelserv, I'm happy to offer you a few words about your setup posted in #56.
Your service-start looks okay. The line to start pixelserv-tls is redundant although it doesn't hurt either. As you install pixelserv-tls from Entware-ng, it'll be automatically started as part of rc.unslung that follows. To keep it simple, you can simply remove the pixelserv-tls line.
Looking at your servstats, it shows you haven't created ca.crt and ca.key, follow the simple steps here to get them created. I would at the minimum get this CA cert created.
Optionally you would want to import ca.crt into your client devices. Follow the steps here. Don't feel obliged to import ca.crt. Without it your client devices just work (contrary to the opposite belief) with no ill effect. Personally I don't bother import ca.crt into my TV, internet radio etc. I only import on my major browsing devices such as phones, tablets and PC.
Since I'm looking at your services-start, I would simply unload my rant. I have huge issue with ill advice scattered on this forum that I saw before. It's bad idea to add a few seconds of sleep here and there as well as polling loops in various "custom scripts". A better place to start Entware-ng will be to call rc.unslung inside post-mount (not services-start). You can read my example posted here: http://www.snbforums.com/threads/syncthing-ac68u.27030/#post-207695. There you won't need the "until" polling loop for pen drive to be available. The 1 second sleep will go too. Anyway, just my attempt to help you having a robust system. You don't have to change if your main focus is simply functionality.
Your service-start looks okay. The line to start pixelserv-tls is redundant although it doesn't hurt either. As you install pixelserv-tls from Entware-ng, it'll be automatically started as part of rc.unslung that follows. To keep it simple, you can simply remove the pixelserv-tls line.
Looking at your servstats, it shows you haven't created ca.crt and ca.key, follow the simple steps here to get them created. I would at the minimum get this CA cert created.
Optionally you would want to import ca.crt into your client devices. Follow the steps here. Don't feel obliged to import ca.crt. Without it your client devices just work (contrary to the opposite belief) with no ill effect. Personally I don't bother import ca.crt into my TV, internet radio etc. I only import on my major browsing devices such as phones, tablets and PC.
Since I'm looking at your services-start, I would simply unload my rant. I have huge issue with ill advice scattered on this forum that I saw before. It's bad idea to add a few seconds of sleep here and there as well as polling loops in various "custom scripts". A better place to start Entware-ng will be to call rc.unslung inside post-mount (not services-start). You can read my example posted here: http://www.snbforums.com/threads/syncthing-ac68u.27030/#post-207695. There you won't need the "until" polling loop for pen drive to be available. The 1 second sleep will go too. Anyway, just my attempt to help you having a robust system. You don't have to change if your main focus is simply functionality.
Thank you very much for your detailed@IngoPan, since you're running pixelserv, I'm happy to offer you a few words about your setup posted in #56.
Your service-start looks okay. The line to start pixelserv-tls is redundant although it doesn't hurt either. As you install pixelserv-tls from Entware-ng, it'll be automatically started as part of rc.unslung that follows. To keep it simple, you can simply remove the pixelserv-tls line.
Looking at your servstats, it shows you haven't created ca.crt and ca.key, follow the simple steps here to get them created. I would at the minimum get this CA cert created.
Optionally you would want to import ca.crt into your client devices. Follow the steps here. Don't feel obliged to import ca.crt. Without it your client devices just work (contrary to the opposite belief) with no ill effect. Personally I don't bother import ca.crt into my TV, internet radio etc. I only import on my major browsing devices such as phones, tablets and PC.
Since I'm looking at your services-start, I would simply unload my rant. I have huge issue with ill advice scattered on this forum that I saw before. It's bad idea to add a few seconds of sleep here and there as well as polling loops in various "custom scripts". A better place to start Entware-ng will be to call rc.unslung inside post-mount (not services-start). You can read my example posted here: http://www.snbforums.com/threads/syncthing-ac68u.27030/#post-207695. There you won't need the "until" polling loop for pen drive to be available. The 1 second sleep will go too. Anyway, just my attempt to help you having a robust system. You don't have to change if your main focus is simply functionality.
guide. I will do the required steps and let you know shortly. Maybe you should add the certificate partbto the first post. Thanks for heads up. I really appreciate it.
Gesendet von meinem SM-G935F mit Tapatalk
- Status
Similar threads
| Thread starter | Title | Forum | Replies | Date |
|---|---|---|---|---|
|
Reconfiguring system - which approach? | Asuswrt-Merlin | 5 |