Menu
What's new
By:
Filters Better Search

How to disable Windows 10 tracking using ipset + Entware

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

Is anyone having ipset problems using Win10tracking with 380.57? The problem I'm having is...

admin@RT-AC68U-F000:/jffs/scripts# sh firewall-start

Done.
iptables v1.4.14: Set Win10tracking doesn't exist.

Try `iptables -h' or 'iptables --help' for more information.
admin@RT-AC68U-F000:/jffs/scripts# ipset --list Win10tracking
ipset v4.5: Unknown set
 
TheOldMan said:
Is anyone having ipset problems using Win10tracking with 380.57? The problem I'm having is...

admin@RT-AC68U-F000:/jffs/scripts# sh firewall-start

Done.
iptables v1.4.14: Set Win10tracking doesn't exist.

Try `iptables -h' or 'iptables --help' for more information.
admin@RT-AC68U-F000:/jffs/scripts# ipset --list Win10tracking
ipset v4.5: Unknown set
Click to expand...

I am able to do a cat on /jffs/Win10tracking.txt, /jffs/scripts/firewall-start and /jffs/configs/dnsmasq.conf.add. ipset -L returns nothing. Checking ipset -V lists correct version. Just that the shebang seems to contain an error. It says cannot find Win10tracking or Win10tracking.txt ... Hope this helps to figure out the problem? 378.56_2 and the 380.57 alphas had no ipset errors. The 380.57 release gives the ipset errors...
 
Last edited:
I figured out the error. The script does not work if it is wordwrapped. Unwrapped it in nano and it's working again. Make sure the script is in one line before the semicolon. I guess as I do not have a shebang tester. Alls good and well. It became sensitive after 380.57.
 
Is script in first post still working for blocking win 10 tracking?

sent from Kodi 17 Krypton
 
i installed this win 1o tracking script. i put this into terminal and got this...is this ok:
Code: 
ipset --list Win10tracking
Code: 
login as: xxxxx
xxxxx@xxx.xxx.x.x's password:


ASUSWRT-Merlin RT-AC68U_3.0.0.4 Thu Dec 24 18:54:10 UTC 2015
admin@RT-AC68U:/tmp/home/root# ipset --list Win10tracking
Name: Win10tracking
Type: iphash
References: 1
Header: hashsize: 1024 probes: 8 resize: 50
Members:

admin@RT-AC68U:/tmp/home/root#

and at syslog i got all that dnsmasq addresses...is that normal or i can to disable this? where to see if the script blocking something?
Code: 
Feb 19 09:30:10 dnsmasq[1374]: using nameserver 127.0.0.1#1919 for domain www.msftncsi.com

Feb 19 09:30:10 dnsmasq[1374]: using nameserver 127.0.0.1#1919 for domain s0.2mdn.net
Feb 19 09:30:10 dnsmasq[1374]: using nameserver 127.0.0.1#1919 for domain s.gateway.messenger.live.com
Feb 19 09:30:10 dnsmasq[1374]: using nameserver 127.0.0.1#1919 for domain reports.wes.df.telemetry.microsoft.com
Feb 19 09:30:10 dnsmasq[1374]: using nameserver 127.0.0.1#1919 for domain redir.metaservices.microsoft.com
Feb 19 09:30:10 dnsmasq[1374]: using nameserver 127.0.0.1#1919 for domain rad.msn.com
Feb 19 09:30:10 dnsmasq[1374]: using nameserver 127.0.0.1#1919 for domain rad.live.com
Feb 19 09:30:10 dnsmasq[1374]: using nameserver 127.0.0.1#1919 for domain pricelist.skype.com
Feb 19 09:30:10 dnsmasq[1374]: using nameserver 127.0.0.1#1919 for domain preview.msn.com
Feb 19 09:30:10 dnsmasq[1374]: using nameserver 127.0.0.1#1919 for domain pre.footprintpredict.com
Feb 19 09:30:10 dnsmasq[1374]: using nameserver 127.0.0.1#1919 for domain oca.telemetry.microsoft.com.nsatc.net
Feb 19 09:30:10 dnsmasq[1374]: using nameserver 127.0.0.1#1919 for domain oca.telemetry.microsoft.com
Feb 19 09:30:10 dnsmasq[1374]: using nameserver 127.0.0.1#1919 for domain msntest.serving-sys.com
Feb 19 09:30:10 dnsmasq[1374]: using nameserver 127.0.0.1#1919 for domain msnbot-65-55-108-23.search.msn.com
Feb 19 09:30:10 dnsmasq[1374]: using nameserver 127.0.0.1#1919 for domain msftncsi.com
Feb 19 09:30:10 dnsmasq[1374]: using nameserver 127.0.0.1#1919 for domain msedge.net
Feb 19 09:30:10 dnsmasq[1374]: using nameserver 127.0.0.1#1919 for domain m.hotmail.com
Feb 19 09:30:10 dnsmasq[1374]: using nameserver 127.0.0.1#1919 for domain m.adnxs.com
Feb 19 09:30:10 dnsmasq[1374]: using nameserver 127.0.0.1#1919 for domain live.rads.msn.com
Feb 19 09:30:10 dnsmasq[1374]: using nameserver 127.0.0.1#1919 for domain lb1.www.ms.akadns.net
Feb 19 09:30:10 dnsmasq[1374]: using nameserver 127.0.0.1#1919 for domain i1.services.social.microsoft.com.nsatc.net
Feb 19 09:30:10 dnsmasq[1374]: using nameserver 127.0.0.1#1919 for domain i1.services.social.microsoft.com
Feb 19 09:30:10 dnsmasq[1374]: using nameserver 127.0.0.1#1919 for domain h1.msn.com
Feb 19 09:30:10 dnsmasq[1374]: using nameserver 127.0.0.1#1919 for domain g.msn.com
Feb 19 09:30:10 dnsmasq[1374]: using nameserver 127.0.0.1#1919 for domain flex.msn.com
Feb 19 09:30:10 dnsmasq[1374]: using nameserver 127.0.0.1#1919 for domain feedback.windows.com
Feb 19 09:30:10 dnsmasq[1374]: using nameserver 127.0.0.1#1919 for domain feedback.search.microsoft.com
Feb 19 09:30:10 dnsmasq[1374]: using nameserver 127.0.0.1#1919 for domain feedback.microsoft-hohm.com
Feb 19 09:30:10 dnsmasq[1374]: using nameserver 127.0.0.1#1919 for domain fe2.update.microsoft.com.akadns.net
Feb 19 09:30:10 dnsmasq[1374]: using nameserver 127.0.0.1#1919 for domain ec.atdmt.com
Feb 19 09:30:10 dnsmasq[1374]: using nameserver 127.0.0.1#1919 for domain diagnostics.support.microsoft.com
Feb 19 09:30:10 dnsmasq[1374]: using nameserver 127.0.0.1#1919 for domain df.telemetry.microsoft.com
Feb 19 09:30:10 dnsmasq[1374]: using nameserver 127.0.0.1#1919 for domain db3aqu.atdmt.com
Feb 19 09:30:10 dnsmasq[1374]: using nameserver 127.0.0.1#1919 for domain cs1.wpc.v0cdn.net
Feb 19 09:30:10 dnsmasq[1374]: using nameserver 127.0.0.1#1919 for domain corpext.msitadfs.glbdns2.microsoft.com
Feb 19 09:30:10 dnsmasq[1374]: using nameserver 127.0.0.1#1919 for domain corp.sts.microsoft.com
Feb 19 09:30:10 dnsmasq[1374]: using nameserver 127.0.0.1#1919 for domain compatexchange.cloudapp.net
Feb 19 09:30:10 dnsmasq[1374]: using nameserver 127.0.0.1#1919 for domain choice.microsoft.com.nsatc.net
Feb 19 09:30:10 dnsmasq[1374]: using nameserver 127.0.0.1#1919 for domain choice.microsoft.com
Feb 19 09:30:10 dnsmasq[1374]: using nameserver 127.0.0.1#1919 for domain cds26.ams9.msecn.net
Feb 19 09:30:10 dnsmasq[1374]: using nameserver 127.0.0.1#1919 for domain cdn.atdmt.com
Feb 19 09:30:10 dnsmasq[1374]: using nameserver 127.0.0.1#1919 for domain c.msn.com
Feb 19 09:30:10 dnsmasq[1374]: using nameserver 127.0.0.1#1919 for domain c.atdmt.com
Feb 19 09:30:10 dnsmasq[1374]: using nameserver 127.0.0.1#1919 for domain bs.serving-sys.com
Feb 19 09:30:10 dnsmasq[1374]: using nameserver 127.0.0.1#1919 for domain b.rad.msn.com
Feb 19 09:30:10 dnsmasq[1374]: using nameserver 127.0.0.1#1919 for domain b.ads2.msads.net
Feb 19 09:30:10 dnsmasq[1374]: using nameserver 127.0.0.1#1919 for domain b.ads1.msn.com
Feb 19 09:30:10 dnsmasq[1374]: using nameserver 127.0.0.1#1919 for domain az512334.vo.msecnd.net
Feb 19 09:30:10 dnsmasq[1374]: using nameserver 127.0.0.1#1919 for domain az361816.vo.msecnd.net
Feb 19 09:30:10 dnsmasq[1374]: using nameserver 127.0.0.1#1919 for domain apps.skype.com
Feb 19 09:30:10 dnsmasq[1374]: using nameserver 127.0.0.1#1919 for domain a-msedge.net
Feb 19 09:30:10 dnsmasq[1374]: using nameserver 127.0.0.1#1919 for domain aka-cdn-ns.adtech.de
Feb 19 09:30:10 dnsmasq[1374]: using nameserver 127.0.0.1#1919 for domain aidps.atdmt.com
Feb 19 09:30:10 dnsmasq[1374]: using nameserver 127.0.0.1#1919 for domain ads1.msn.com
Feb 19 09:30:10 dnsmasq[1374]: using nameserver 127.0.0.1#1919 for domain ads1.msads.net
Feb 19 09:30:10 dnsmasq[1374]: using nameserver 127.0.0.1#1919 for domain ads.msn.com
Feb 19 09:30:10 dnsmasq[1374]: using nameserver 127.0.0.1#1919 for domain adnxs.com
Feb 19 09:30:10 dnsmasq[1374]: using nameserver 127.0.0.1#1919 for domain adnexus.net
Feb 19 09:30:10 dnsmasq[1374]: using nameserver 127.0.0.1#1919 for domain ad.doubleclick.net
Feb 19 09:30:10 dnsmasq[1374]: using nameserver 127.0.0.1#1919 for domain ac3.msn.com
Feb 19 09:30:10 dnsmasq[1374]: using nameserver 127.0.0.1#1919 for domain a-0009.a-msedge.net
Feb 19 09:30:10 dnsmasq[1374]: using nameserver 127.0.0.1#1919 for domain a-0008.a-msedge.net
Feb 19 09:30:10 dnsmasq[1374]: using nameserver 127.0.0.1#1919 for domain a-0007.a-msedge.net
Feb 19 09:30:10 dnsmasq[1374]: using nameserver 127.0.0.1#1919 for domain a-0006.a-msedge.net
Feb 19 09:30:10 dnsmasq[1374]: using nameserver 127.0.0.1#1919 for domain a-0005.a-msedge.net
Feb 19 09:30:10 dnsmasq[1374]: using nameserver 127.0.0.1#1919 for domain a-0004.a-msedge.net
Feb 19 09:30:10 dnsmasq[1374]: using nameserver 127.0.0.1#1919 for domain a-0003.a-msedge.net
Feb 19 09:30:10 dnsmasq[1374]: using nameserver 127.0.0.1#1919 for domain a-0002.a-msedge.net
Feb 19 09:30:10 dnsmasq[1374]: using nameserver 127.0.0.1#1919 for domain a-0001.a-msedge.net
Feb 19 09:30:10 dnsmasq[1374]: using nameserver 127.0.0.1#1919 for domain a.rad.msn.com
Feb 19 09:30:10 dnsmasq[1374]: using nameserver 127.0.0.1#1919 for domain a.ads2.msn.com
Feb 19 09:30:10 dnsmasq[1374]: using nameserver 127.0.0.1#1919 for domain a.ads2.msads.net
Feb 19 09:30:10 dnsmasq[1374]: using nameserver 127.0.0.1#1919 for domain a.ads1.msn.com
 
cosmoxl said:
looks right to me. you can also use the command ipset -L eventually you should see a list of IP addresses that were blocked.
Click to expand...
is possible to stop writing in syslog this kind dnsmasq?
Code: 
dnsmasq[1374]: using nameserver 127.0.0.1#1919 for domain i1.services.social.microsoft.com
 
bayern1975 said:
is possible to stop writing in syslog this kind dnsmasq?
Code: 
dnsmasq[1374]: using nameserver 127.0.0.1#1919 for domain i1.services.social.microsoft.com
Click to expand...

somebody else would have to answer this. I don't know.
 
TheOldMan said:
I figured out the error. The script does not work if it is wordwrapped. Unwrapped it in nano and it's working again. Make sure the script is in one line before the semicolon. I guess as I do not have a shebang tester. Alls good and well. It became sensitive after 380.57.
Click to expand...
Can you by any chance upload the unwrapped script? I'll be happy to test it.
 
hello, still do not know if possible to stop write this kinds logs in syslog with windows 10 tracking script? any solution for this?
Code: 
Feb 19 09:30:10 dnsmasq[1374]: using nameserver 127.0.0.1#1919 for domain www.msftncsi.com
Feb 19 09:30:10 dnsmasq[1374]: using nameserver 127.0.0.1#1919 for domain s0.2mdn.net
Feb 19 09:30:10 dnsmasq[1374]: using nameserver 127.0.0.1#1919 for domain s.gateway.messenger.live.com
Feb 19 09:30:10 dnsmasq[1374]: using nameserver 127.0.0.1#1919 for domain reports.wes.df.telemetry.microsoft.com
Feb 19 09:30:10 dnsmasq[1374]: using nameserver 127.0.0.1#1919 for domain redir.metaservices.microsoft.com
Feb 19 09:30:10 dnsmasq[1374]: using nameserver 127.0.0.1#1919 for domain rad.msn.com
Feb 19 09:30:10 dnsmasq[1374]: using nameserver 127.0.0.1#1919 for domain rad.live.com
Feb 19 09:30:10 dnsmasq[1374]: using nameserver 127.0.0.1#1919 for domain pricelist.skype.com
 
bayern1975 said:
hello, still do not know if possible to stop write this kinds logs in syslog with windows 10 tracking script? any solution for this?
Code: 
Feb 19 09:30:10 dnsmasq[1374]: using nameserver 127.0.0.1#1919 for domain www.msftncsi.com
Feb 19 09:30:10 dnsmasq[1374]: using nameserver 127.0.0.1#1919 for domain s0.2mdn.net
Feb 19 09:30:10 dnsmasq[1374]: using nameserver 127.0.0.1#1919 for domain s.gateway.messenger.live.com
Feb 19 09:30:10 dnsmasq[1374]: using nameserver 127.0.0.1#1919 for domain reports.wes.df.telemetry.microsoft.com
Feb 19 09:30:10 dnsmasq[1374]: using nameserver 127.0.0.1#1919 for domain redir.metaservices.microsoft.com
Feb 19 09:30:10 dnsmasq[1374]: using nameserver 127.0.0.1#1919 for domain rad.msn.com
Feb 19 09:30:10 dnsmasq[1374]: using nameserver 127.0.0.1#1919 for domain rad.live.com
Feb 19 09:30:10 dnsmasq[1374]: using nameserver 127.0.0.1#1919 for domain pricelist.skype.com
Click to expand...
As part of the upcoming AB-Solution 1.1 release as an add-on, these entries will log to the dnsmasq logfile, if logging is enabled.
 
thelonelycoder said:
As part of the upcoming AB-Solution 1.1 release as an add-on, these entries will log to the dnsmasq logfile, if logging is enabled.
Click to expand...
yes i understand....but with this currently script these entries write in logfile every hour.....so there are hundreds of these logs.....this is annoying....
 
Just wondering if this is still working for anyone?

I get zero members in the list after manually trying to connect to some to the sites (which succeed)
admin@RT-AC68U-8858:/tmp/home/root# ipset --list
Name: Win10tracking
Type: iphash
References: 1
Header: hashsize: 1024 probes: 8 resize: 50
Members:

I have tried the old version and the more recent one documented in the wiki..

Thanks
GF
 
TheOldMan said:
I figured out the error. The script does not work if it is wordwrapped. Unwrapped it in nano and it's working again. Make sure the script is in one line before the semicolon. I guess as I do not have a shebang tester. Alls good and well. It became sensitive after 380.57.
Click to expand...
I have Merlin fork 374.43_2-16E1 and the same problem:
Code: 
admin@RT-N16-48C5:/tmp/home/root# ipset --list Win10tracking
ipset v4.5: Unknown set

Can you please give unwrapped script?
 
Vik said:
I have Merlin fork 374.43_2-16E1 and the same problem:
Code: 
admin@RT-N16-48C5:/tmp/home/root# ipset --list Win10tracking
ipset v4.5: Unknown set

Can you please give unwrapped script?
Click to expand...

I'm using John's fork also. The easy way is just to use AB-Solution and insert the following in /tmp/mnt/sda1/adblocking.

Code: 
#Microsoft
0.0.0.0 a-0001.a-msedge.net
0.0.0.0 a-0002.a-msedge.net
0.0.0.0 a-0003.a-msedge.net
0.0.0.0 a-0004.a-msedge.net
0.0.0.0 a-0005.a-msedge.net
0.0.0.0 a-0006.a-msedge.net
0.0.0.0 a-0007.a-msedge.net
0.0.0.0 a-0008.a-msedge.net
0.0.0.0 a-0009.a-msedge.net
0.0.0.0 a-msedge.net
0.0.0.0 a.ads1.msn.com
0.0.0.0 a.ads2.msads.net
0.0.0.0 a.ads2.msn.com
0.0.0.0 a.rad.msn.com
0.0.0.0 a0001.a-msedge.net
0.0.0.0 a0002.a-msedge.net
0.0.0.0 a0003.a-msedge.net
0.0.0.0 a0004.a-msedge.net
0.0.0.0 a0005.a-msedge.net
0.0.0.0 a0006.a-msedge.net
0.0.0.0 a0007.a-msedge.net
0.0.0.0 a0008.a-msedge.net
0.0.0.0 a0009.a-msedge.net
0.0.0.0 a1621.g.akamai.net
0.0.0.0 a1856.g2.akamai.net
0.0.0.0 a1961.g.akamai.net
0.0.0.0 a23-218-212-69.deploy.static.akamaitechnologies.com
0.0.0.0 a248.e.akamai.net
0.0.0.0 a978.i6g1.akamai.net
0.0.0.0 ac3.msn.com
0.0.0.0 ad.doubleclick.net
0.0.0.0 adnexus.net
0.0.0.0 adnxs.com
0.0.0.0 ads.msn.com
0.0.0.0 ads1.msads.net
0.0.0.0 ads1.msn.com
0.0.0.0 aidps.atdmt.com
0.0.0.0 aka-cdn-ns.adtech.de
0.0.0.0 aka.ms
0.0.0.0 americas2.notify.windows.com.akadns.net
0.0.0.0 any.edge.bing.com
0.0.0.0 apps.skype.com
0.0.0.0 atlas.c10r.facebook.com
0.0.0.0 az361816.vo.msecnd.net
0.0.0.0 az512334.vo.msecnd.net
0.0.0.0 b.ads1.msn.com
0.0.0.0 b.ads2.msads.net
0.0.0.0 b.rad.msn.com
0.0.0.0 bing.com
0.0.0.0 bingads.microsoft.com
0.0.0.0 bl3302.storage.live.com
0.0.0.0 bl3302geo.storage.dkyprod.akadns.net
0.0.0.0 bn1wns2011508.wns.windows.com
0.0.0.0 bs.serving-sys.com
0.0.0.0 c-0001.c-msedge.net
0.0.0.0 c.atdmt.com
0.0.0.0 c.msn.com
0.0.0.0 c.msn.com.nsatc.net
0.0.0.0 cdn.atdmt.com
0.0.0.0 cdnjs.cloudflare.com.cdn.cloudflare.net
0.0.0.0 cdp1.public-trust.com
0.0.0.0 cds26.ams9.msecn.net
0.0.0.0 choice.microsoft.com
0.0.0.0 choice.microsoft.com.nsatc.net
0.0.0.0 client.wns.windows.com
0.0.0.0 compatexchange.cloudapp.net
0.0.0.0 corp.sts.microsoft.com
0.0.0.0 corpext.msitadfs.glbdns2.microsoft.com
0.0.0.0 cs1.wpc.v0cdn.net
0.0.0.0 cy2.displaycatalog.md.mp.microsoft.com.akadns.net
0.0.0.0 db3aqu.atdmt.com
0.0.0.0 dc.services.visualstudio.com
0.0.0.0 df.telemetry.microsoft.com
0.0.0.0 diagnostics.support.microsoft.com
0.0.0.0 directory.services.live.com
0.0.0.0 directory.services.live.com.akadns.net
0.0.0.0 dns.msftncsi.com
0.0.0.0 download-ssl.msgamestudios.com
0.0.0.0 dt.adsafeprotected.com
0.0.0.0 e-0009.e-msedge.net
0.0.0.0 e2835.dspb.akamaiedge.net
0.0.0.0 e7341.g.akamaiedge.net
0.0.0.0 e7502.ce.akamaiedge.net
0.0.0.0 e8218.ce.akamaiedge.net
0.0.0.0 ec.atdmt.com
0.0.0.0 en-us.appex-rf.msn.com
0.0.0.0 eu.vortex.data.microsoft.com
0.0.0.0 fe2.update.microsoft.com.akadns.net
0.0.0.0 fe2.ws.microsoft.com.nsatc.net
0.0.0.0 fe3.delivery.dsp.mp.microsoft.com.nsatc.net
0.0.0.0 fe3.delivery.mp.microsoft.com
0.0.0.0 feedback.microsoft-hohm.com
0.0.0.0 feedback.search.microsoft.com
0.0.0.0 feedback.windows.com
0.0.0.0 flex.msn.com
0.0.0.0 fw.adsafeprotected.com
0.0.0.0 g.msn.com
0.0.0.0 go.microsoft.com
0.0.0.0 googleads4.g.doubleclick.net
0.0.0.0 h1.msn.com
0.0.0.0 hostedocsp.globalsign.com
0.0.0.0 i1.services.social.microsoft.com
0.0.0.0 i1.services.social.microsoft.com.nsatc.net
0.0.0.0 ieonlinews.microsoft.com
0.0.0.0 inference.location.livenet.akadns.net
0.0.0.0 ipv6.msftncsi.com
0.0.0.0 ipv6.msftncsi.com.edgesuite.net
0.0.0.0 lb1.www.ms.akadns.net
0.0.0.0 li581-132.members.linode.com
0.0.0.0 licensing.md.mp.microsoft.com
0.0.0.0 live.rads.msn.com
0.0.0.0 login.live.com
0.0.0.0 login.live.com.nsatc.net
0.0.0.0 m.adnxs.com
0.0.0.0 m.hotmail.com
0.0.0.0 m221.absolute.com
0.0.0.0 mobileads.msn.com
0.0.0.0 mpd.mxptint.net
0.0.0.0 mscrl.microsoft.com
0.0.0.0 msedge.net
0.0.0.0 msftncsi.com
0.0.0.0 msnbot-65-55-108-23.search.msn.com
0.0.0.0 msntest.serving-sys.com
0.0.0.0 ns1.msft.net
0.0.0.0 ns2.msft.net
0.0.0.0 ns3.msft.net
0.0.0.0 ns4.msft.net
0.0.0.0 ns5.msft.net
0.0.0.0 ns6.msft.net
0.0.0.0 oca.telemetry.microsoft.com
0.0.0.0 oca.telemetry.microsoft.com.nsatc.net
0.0.0.0 OneSettings-bn2.metron.live.com.nsatc.net
0.0.0.0 onesettings-cy2.metron.live.com.nsatc.net
0.0.0.0 origin.windows.microsoft.com.akadns.net
0.0.0.0 osiprod-scus-snow-000.cloudapp.net
0.0.0.0 pre.footprintpredict.com
0.0.0.0 preview.msn.com
0.0.0.0 pricelist.skype.com
0.0.0.0 prod-w.nexus.live.com.akadns.net
0.0.0.0 rad.live.com
0.0.0.0 rad.msn.com
0.0.0.0 redir.metaservices.microsoft.com
0.0.0.0 register.mesh.com
0.0.0.0 reports.wes.df.telemetry.microsoft.com
0.0.0.0 s.gateway.messenger.live.com
0.0.0.0 sc.iasds01.com
0.0.0.0 schemas.microsoft.akadns.net
0.0.0.0 secure.adnxs.com
0.0.0.0 secure.flashtalking.com
0.0.0.0 services.wes.df.telemetry.microsoft.com
0.0.0.0 settings-sandbox.data.microsoft.com
0.0.0.0 settings-win.data.microsoft.com
0.0.0.0 settings.data.glbdns2.microsoft.com
0.0.0.0 skyapi.live.net
0.0.0.0 skyapi.skyprod.akadns.net
0.0.0.0 skydrive.wns.windows.com
0.0.0.0 sls.update.microsoft.com.akadns.net
0.0.0.0 sm.mcafee.com
0.0.0.0 so.2mdn.net
0.0.0.0 solitaireprod.maelstrom.xboxlive.com
0.0.0.0 spynetus.microsoft.akadns.net
0.0.0.0 sqm.df.telemetry.microsoft.com
0.0.0.0 sqm.telemetry.microsoft.com
0.0.0.0 sqm.telemetry.microsoft.com.nsatc.net
0.0.0.0 ssw.live.com
0.0.0.0 ssw.live.com.nsatc.net
0.0.0.0 static.2mdn.net
0.0.0.0 statsfe1.ws.microsoft.com
0.0.0.0 statsfe2.update.microsoft.com.akadns.net
0.0.0.0 statsfe2.ws.microsoft.com
0.0.0.0 storeedgefd.dsx.mp.microsoft.com
0.0.0.0 su3.mcafee.com
0.0.0.0 survey.watson.microsoft.com
0.0.0.0 telecommand.telemetry.microsoft.com
0.0.0.0 telecommand.telemetry.microsoft.com.nsatc.net
0.0.0.0 telemetry.appex.bing.net
0.0.0.0 telemetry.appex.bing.net:443
0.0.0.0 telemetry.microsoft.com
0.0.0.0 telemetry.urs.microsoft.com
0.0.0.0 travel.tile.appex.bing.com
0.0.0.0 tunnel.cfw.trustedsource.org
0.0.0.0 ui.skype.com
0.0.0.0 updatekeepalive.mcafee.com
0.0.0.0 urs.microsoft.com.nsatc.net
0.0.0.0 v10.vortex-win.data.metron.life.com.nsatc.net
0.0.0.0 v10.vortex-win.data.microsoft.com
0.0.0.0 view.atdmt.com
0.0.0.0 vortex-bn2.metron.live.com.nsatc.net
0.0.0.0 vortex-cy2.metron.live.com.nsatc.net
0.0.0.0 vortex-hk2.metron.live.com.nsatc.net
0.0.0.0 vortex-sandbox.data.microsoft.com
0.0.0.0 vortex-win.data.microsoft.com
0.0.0.0 vortex.data.microsoft.com
0.0.0.0 watson.live.com
0.0.0.0 watson.microsoft.com
0.0.0.0 watson.ppe.telemetry.microsoft.com
0.0.0.0 watson.telemetry.microsoft.com
0.0.0.0 watson.telemetry.microsoft.com.nsatc.net
0.0.0.0 wes.df.telemetry.microsoft.com
0.0.0.0 wildcard.appex-rf.msn.com.edgesuite.net
0.0.0.0 wildcard.twimg.com
0.0.0.0 win10.ipv6.microsoft.com
0.0.0.0 win10.ipv6.microsoft.com.nsatc.net
0.0.0.0 wns.notify.windows.com.akadns.net
0.0.0.0 wns.windows.com
0.0.0.0 www.bing.com
0.0.0.0 www.go.microsoft.akadns.net
#0.0.0.0 fe2.update.microsoft.com.akadns.net # MICROSOFT UPDATE - UNCOMMENT TO BLOCK      
#0.0.0.0 fe2.update.microsoft.com.nsatc.net  # MICROSOFT UPDATE - UNCOMMENT TO BLOCK      
#0.0.0.0 a767.dspw65.akamai.net              # MICROSOFT UPDATE - UNCOMMENT TO BLOCK        
#0.0.0.0 sls.update.microsoft.com.akadns.net # MICROSOFT UPDATE - UNCOMMENT TO BLOCK        
#0.0.0.0 ui.skype.com                        # MICROSOFT SKYPE - UNCOMMENT TO BLOCK        
#0.0.0.0 pricelist.skype.com                 # MICROSOFT SKYPE - UNCOMMENT TO BLOCK        
#0.0.0.0 apps.skype.com                      # MICROSOFT SKYPE - UNCOMMENT TO BLOCK
 
Last edited:
jeff288 said:
I'm using John's fork also. The easy way is just to use AB-Solution and insert the following in /tmp/mnt/sda1/adblocking.
Click to expand...

I have previously looked at that but does that actually solve the problem though? Read ryzhov_al post below

ryzhov_al said:
Please refer to this how-to on asuswrt-merlin releases newer then 378.55. Solution below is for 378.55 version and older.
Some guides offers to block unwanted sites via hosts file, but it's not working (in some cases) with Windows 10, which can detect DNS resolution is changed by user and use hardcoded IP addresses. So, it's better to resolve DNS names right and block traffic to this sites later.
My solution includes two independent parts:
  • creating set of unwanted IPs with ipset and block it with iptables. It's a part from firmware.
  • adding new unwanted IPs with ipset-dns. This is part from Entware.
Click to expand...
 
G F said:
I have previously looked at that but does that actually solve the problem though? Read ryzhov_al post below
Click to expand...

That works by using NCSI as a workaround which you can disable according to the link provided and it's, if we trust MS, only for detecting your network status so the network icon can tell us when we're connected which I'm personally not concerned about. Of course, I haven't done any comprehensive testing of it as I just mostly wanted the malware protection.
 
G F said:
I have previously looked at that but does that actually solve the problem though? Read ryzhov_al post below
Click to expand...
V14 of my fork picked up ipset support, so as far as the quote, V14 and newer is the equivalent of 378.55 and newer.
 
Thanks John. Just for clarification im running Merlin 380.58 and still have this issue.
 
You must log in or register to reply here.

Similar threads

Martineau
How to Dynamically Ban Malicious IP's using IPSet (Martineau version)
20 21 22
Replies
438
Views
53K
Jack Yaz
Jack Yaz
Similar threads
Thread starter Title Forum Replies Date
R Disable Intranet access for a LAN port (not the WiFi Guest network)? Asuswrt-Merlin 10
T GT BE98 Pro Guest Network Cannot Disable Intranet Access Asuswrt-Merlin 3
Q How to permanently disable autoconf on router (wsdd2 and avahi-daemon) Asuswrt-Merlin 2
A Any way to disable the ASUSTek Hidden Networks? Asuswrt-Merlin 12
Tom Jo-Jo Junior Shabadoo Disable A record ASUS DDNS Asuswrt-Merlin 2
saison2023 Any way to disable/prevent start of a script without uninstalling it ? Asuswrt-Merlin 4
wcoastsands RT-AX88U Guest Network connection issue when Access Intranet is set to Disable Asuswrt-Merlin 5
L Wireguard with vpn director rules disable hardware acceleration? Asuswrt-Merlin 15
T Wireguard VPN Disable IPV6 Asuswrt-Merlin 0
D Disable kernel module Asuswrt-Merlin 1

Similar threads

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!

Members online

Total: 564 (members: 31, guests: 533)
Top