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!

I run three instances of dnscrypt-proxy on the Asuswrt-Merlin router, on ports 60053-60055, and I want to use it with ipset-dns. However, ipset-dns does not allow the user to specify the port number of the upstream DNS resolver.

How to do it:
Code: 
# start ipset-dns with a bogus upstream DNS resolver
ipset-dns Win10tracking Win10tracking 1919 1.1.1.1

# redirect the bogus upstream DNS resolver to dnscrypt-proxy
iptables -t nat -I OUTPUT -d 1.1.1.1 -p tcp --dport 53 -j REDIRECT --to-ports 60053-60055
iptables -t nat -I OUTPUT -d 1.1.1.1 -p udp --dport 53 -j REDIRECT --to-ports 60053-60055
 
Last edited:
Just a warning for the upcoming releases of firmware that will support dnsmasq with ipset...

If you leave the ipset commands added to the dnsmasq,conf.add file and attempt to downlevel the firmware to a level that does not support dnsmasq with ipset, dnsmasq will fail to start and you will not be able to gain access to the router.

@ryzhov_al - You may want to think about adding a check to your script to see if it is supported and aborting the ipset adds (and clear any existing adds) if dnsmasq doesn't support ipset.
 
john9527 said:
dnsmasq will fail to start and you will not be able to gain access to the router.
Click to expand...
A use for the dnsmasq.postconf? Like this:

/jffs/scripts/dnsmasq.postconf
Code: 
#!/bin/sh
dnsmasq -v | grep -i "no-ipset" > /dev/null 2>&1
if [ $? -eq 0 ]; then
  # dnsmasq does not have ipset support
  echo "conf-file=/jffs/configs/dnsmasq.ipsetdns.conf" >> "$1"
else
  # dnsmasq has ipset support
  echo "conf-file=/jffs/configs/dnsmasq.ipset.conf" >> "$1"
fi
 
Gona try this again does this look right??

Code: 
cat << EOF >/jffs/Win10tracking.txt
a.ads1.msn.com
a.ads2.msads.net
a.ads2.msn.com
a.rad.msn.com
a-0001.a-msedge.net
a-0002.a-msedge.net
a-0003.a-msedge.net
a-0004.a-msedge.net
a-0005.a-msedge.net
a-0006.a-msedge.net
a-0007.a-msedge.net
a-0008.a-msedge.net
a-0009.a-msedge.net
ac3.msn.com
ad.doubleclick.net
adnexus.net
adnxs.com
ads.msn.com
ads1.msads.net
ads1.msn.com
aidps.atdmt.com
aka-cdn-ns.adtech.de
a-msedge.net
apps.skype.com
az361816.vo.msecnd.net
az512334.vo.msecnd.net
b.ads1.msn.com
b.ads2.msads.net
b.rad.msn.com
bs.serving-sys.com
c.atdmt.com
c.msn.com
cdn.atdmt.com
cds26.ams9.msecn.net
choice.microsoft.com
choice.microsoft.com.nsatc.net
compatexchange.cloudapp.net
corp.sts.microsoft.com
corpext.msitadfs.glbdns2.microsoft.com
cs1.wpc.v0cdn.net
db3aqu.atdmt.com
df.telemetry.microsoft.com
diagnostics.support.microsoft.com
ec.atdmt.com
fe2.update.microsoft.com.akadns.net
feedback.microsoft-hohm.com
feedback.search.microsoft.com
feedback.windows.com
flex.msn.com
g.msn.com
h1.msn.com
i1.services.social.microsoft.com
i1.services.social.microsoft.com.nsatc.net
lb1.www.ms.akadns.net
live.rads.msn.com
m.adnxs.com
m.hotmail.com
msedge.net
msftncsi.com
msnbot-65-55-108-23.search.msn.com
msntest.serving-sys.com
oca.telemetry.microsoft.com
oca.telemetry.microsoft.com.nsatc.net
pre.footprintpredict.com
preview.msn.com
pricelist.skype.com
rad.live.com
rad.msn.com
redir.metaservices.microsoft.com
reports.wes.df.telemetry.microsoft.com
s.gateway.messenger.live.com
s0.2mdn.net
schemas.microsoft.akadns.net
secure.adnxs.com
secure.flashtalking.com
services.wes.df.telemetry.microsoft.com
settings-sandbox.data.microsoft.com
settings-win.data.microsoft.com
sls.update.microsoft.com.akadns.net
sqm.df.telemetry.microsoft.com
sqm.telemetry.microsoft.com
sqm.telemetry.microsoft.com.nsatc.net
static.2mdn.net
statsfe1.ws.microsoft.com
statsfe2.update.microsoft.com.akadns.net
statsfe2.ws.microsoft.com
survey.watson.microsoft.com
telecommand.telemetry.microsoft.com
telecommand.telemetry.microsoft.com.nsatc.net
telemetry.appex.bing.net
telemetry.microsoft.com
telemetry.urs.microsoft.com
view.atdmt.com
vortex.data.microsoft.com
vortex-bn2.metron.live.com.nsatc.net
vortex-cy2.metron.live.com.nsatc.net
vortex-sandbox.data.microsoft.com
vortex-win.data.microsoft.com
watson.live.com
watson.microsoft.com
watson.ppe.telemetry.microsoft.com
watson.telemetry.microsoft.com
watson.telemetry.microsoft.com.nsatc.net
wes.df.telemetry.microsoft.com
www.msftncsi.com
EOF

Code: 
cat << EOF > /jffs/scripts/firewall-start
#!/bin/sh
DNSMASQ_CFG=/jffs/configs/dnsmasq.conf.add
if [ ! -f $DNSMASQ_CFG ] || [ "$(grep Win10tracking $DNSMASQ_CFG)" = "" ];
then
  rm -f $DNSMASQ_CFG
  for i in `cat /jffs/Win10tracking.txt`;
  do
    echo "ipset=/$i/Win10tracking" >> $DNSMASQ_CFG
  done
  service restart_dnsmasq
fi

# Load ipset modules
lsmod | grep "ipt_set" > /dev/null 2>&1 || \
for module in ip_set ip_set_nethash ip_set_iphash ipt_set
do
    insmod $module
done

# Create ip set
if [ "$(ipset --swap Win10tracking Win10tracking 2>&1 | grep 'Unknown set')" != "" ];
then
  ipset -N Win10tracking iphash
fi

# Apply iptables rule
iptables-save | grep Win10tracking > /dev/null 2>&1 || \
  iptables -I FORWARD -m set --set Win10tracking src,dst -j DROP

EOF
 
My router is the RT-AC68U. At router startup, something is triggering a second instance of nat-start. So there are two instances of nat-start, launched at the same time, that run simultaneously. This sometimes causes the creation of duplicate firewall rules, even though I have logic that explicitly checks for an existing firewall rule before creating it. This started happening after implementing my scripts for ad blocking and Microsoft tracking, using ipset-dns. If my nat-start had the ability to acquire a lock and release it when done, it may fix the problem.

Some of my scripts are here just in case you want to see what's going on.

cat /tmp/syslog.log | grep custom
Code: 
Dec 31 19:00:15 init-start: custom script ended [353]
Dec 31 19:00:27 custom config: Appending content of /jffs/configs/hosts.add.
Dec 31 19:00:27 custom config: Appending content of /jffs/configs/dnsmasq.conf.add.
Dec 31 19:00:27 custom script: Running /jffs/scripts/dnsmasq.postconf (args: /etc/dnsmasq.conf)
Dec 31 19:00:27 dnsmasq.postconf: custom script started [494]
Dec 31 19:00:27 dnsmasq.postconf: custom script ended [494]
Dec 31 19:00:28 custom config: Using custom /jffs/configs/smb.conf config file.
Dec 31 19:00:59 custom script: Running /jffs/scripts/services-start
Dec 31 19:00:59 services-start: custom script started [715]
Dec 31 19:01:01 services-start: custom script ended [715]
Dec 31 19:01:01 custom script: Running /jffs/scripts/wan-start (args: 0)
Dec 31 19:01:01 wan-start: custom script started [945]
Dec 31 19:01:03 custom script: Running /jffs/scripts/nat-start
Dec 31 19:01:03 nat-start: custom script started [1058]
Dec 31 19:01:03 custom script: Running /jffs/scripts/nat-start
Dec 31 19:01:04 nat-start: custom script started [1078]
Dec 31 19:01:05 custom script: Running /jffs/scripts/firewall-start (args: eth0)
Dec 31 19:01:05 firewall-start: custom script started [1219]
Dec 31 19:01:05 firewall-rules: custom script started [1229]
Dec 31 19:01:05 custom config: Appending content of /jffs/configs/hosts.add.
Dec 31 19:01:05 custom config: Appending content of /jffs/configs/dnsmasq.conf.add.
Dec 31 19:01:05 custom script: Running /jffs/scripts/dnsmasq.postconf (args: /etc/dnsmasq.conf)
Dec 31 19:01:05 dnsmasq.postconf: custom script started [1255]
Dec 31 19:01:05 nat-start: custom script ended [1078]
Dec 31 19:01:05 nat-start: custom script ended [1058]
Dec 31 19:01:05 dnsmasq.postconf: custom script ended [1255]
Dec 31 19:01:06 firewall-rules: custom script ended [1229]
Dec 31 19:01:06 firewall-start: custom script ended [1219]
Dec 31 19:01:07 custom script: Running /jffs/scripts/post-mount (args: /tmp/mnt/Data)
Dec 31 19:01:07 post-mount: custom script started [1443]
Dec 31 19:01:11 post-mount: custom script ended [1443]
Dec 31 19:01:12 custom config: Using custom /jffs/configs/smb.conf config file.
Dec 31 19:01:12 wan-start: custom script ended [945]
Sep  8 09:26:02 custom config: Appending content of /jffs/configs/hosts.add.
Sep  8 09:26:02 custom config: Appending content of /jffs/configs/dnsmasq.conf.add.
Sep  8 09:26:02 custom script: Running /jffs/scripts/dnsmasq.postconf (args: /etc/dnsmasq.conf)
Sep  8 09:26:02 dnsmasq.postconf: custom script started [1662]
Sep  8 09:26:02 dnsmasq.postconf: custom script ended [1662]

/jffs/scripts/nat-start
Code: 
#!/bin/sh
logger -t $(basename $0) "custom script started [$$]"

/jffs/scripts/nat-rules
/jffs/scripts/ipset-nat-rules

logger -t $(basename $0) "custom script ended [$$]"

/jffs/scripts/firewall-start
Code: 
#!/bin/sh
logger -t $(basename $0) "custom script started [$$]"

/jffs/scripts/firewall-rules
/jffs/scripts/ipset-firewall-rules

logger -t $(basename $0) "custom script ended [$$]"

/jffs/scripts/nat-rules
Code: 
#!/bin/sh
DELETE="$1"

update_rule()
{
  local IPTABLES="$1"
  local CHAIN="$2"
  local RULENUM="$3"
  local RULE="$4"
  local DELETE="$5"

  #echo update_rule $IPTABLES $CHAIN $RULENUM $RULE $DELETE

  if [ "$DELETE" == "delete" ]; then
    ($IPTABLES -C $CHAIN $RULE) > /dev/null 2>&1 && ($IPTABLES -D $CHAIN $RULE)
  else
    ($IPTABLES -C $CHAIN $RULE) > /dev/null 2>&1 || ($IPTABLES -I $CHAIN $RULENUM $RULE)
  fi
}

# route through TOR transparent proxy
#update_rule "iptables -t nat" "PREROUTING" "1" "-i br0 -s xxx.xxx.xxx.xxx -p udp --dport xxx -j REDIRECT --to-ports xxx" "$DELETE"
update_rule "iptables -t nat" "PREROUTING" "1" "-i br0 -p tcp --syn -s xxx.xxx.xxx.xxx ! -d xxx.xxx.xxx.xxx/xxx --match multiport --dports xxx,xxx,xxx,xxx,xxx -j REDIRECT --to-ports xxx" "$DELETE"

# redirect DNS requests to use the router DNS
update_rule "iptables -t nat" "PREROUTING" "1" "-s xxx.xxx.xxx.xxx/xxx -p tcp --dport xxx -j DNAT --to-destination xxx.xxx.xxx.xxx" "$DELETE"
update_rule "iptables -t nat" "PREROUTING" "1" "-s xxx.xxx.xxx.xxx/xxx -p udp --dport xxx -j DNAT --to-destination xxx.xxx.xxx.xxx" "$DELETE"

/jffs/scripts/ipset-nat-rules
Code: 
#!/bin/sh
DELETE="$1"
BLOCKLIST_FOLDER="/jffs/data"
BLOCKLIST_FILE="$BLOCKLIST_FOLDER/blocklists.txt"

update_rule()
{
  local IPTABLES="$1"
  local CHAIN="$2"
  local RULENUM="$3"
  local RULE="$4"
  local DELETE="$5"

  #echo update_rule $IPTABLES $CHAIN $RULENUM $RULE $DELETE

  if [ "$DELETE" == "delete" ]; then
    ($IPTABLES -C $CHAIN $RULE) > /dev/null 2>&1 && ($IPTABLES -D $CHAIN $RULE)
  else
    ($IPTABLES -C $CHAIN $RULE) > /dev/null 2>&1 || ($IPTABLES -I $CHAIN $RULENUM $RULE)
  fi
}

IFS=$','
while read file_name local_port upstream_dns firewall_target
do
  if [ "$firewall_target" != "HOSTSFILE" ]; then
    unset IFS
    FILE_PATH="$BLOCKLIST_FOLDER/$file_name"

    if [ -f $FILE_PATH ]; then
      IPSET_NAME="${file_name%.*}"
      IPSETDNS_CMD="/jffs/bin/ipset-dns $IPSET_NAME $IPSET_NAME $local_port $upstream_dns"
      IPSETDNS_PID=$(echo $(ps w | grep -i "$IPSETDNS_CMD" | grep -v grep) | cut -f1 -d' ')

      if [ "$firewall_target" == "REJECT" ]; then
        PREROUTING_TARGET="REDIRECT --to-ports 81"
      else
        PREROUTING_TARGET="RETURN"
      fi

      # create firewall rule if it does not exist
      update_rule "iptables -t nat" "PREROUTING" "1" "-p tcp -m set --match-set $IPSET_NAME dst -j $PREROUTING_TARGET" "$DELETE"

      if [ "$DELETE" == "delete" ]; then
        # stop ipset-dns if it is running
        [ ! -z "${IPSETDNS_PID##*[!0-9]*}" ] && kill $IPSETDNS_PID
      else
        # create ipset if it does not exist
        if [ "$(ipset --swap $IPSET_NAME $IPSET_NAME 2>&1 | grep 'Unknown set')" != "" ]; then
          ipset -N $IPSET_NAME iphash
        fi

        # start ipset-dns if it is not already running
        [ -z "$IPSETDNS_PID" ] && $IPSETDNS_CMD
      fi
    fi

    IFS=$','
  fi
done < "$BLOCKLIST_FILE"
unset IFS

# redirect DNS requests made by ipset-dns to dnscrypt-proxy
update_rule "iptables -t nat" "OUTPUT" "1" "-d xxx.xxx.xxx.xxx -p udp --dport xxx -j REDIRECT --to-ports xxx-xxx" "$DELETE"

# redirect for NWeb pixelserv
update_rule "iptables -t nat" "PREROUTING" "1" "-d xxx.xxx.xxx.xxx -j RETURN" "$DELETE"
update_rule "iptables -t nat" "PREROUTING" "1" "-d xxx.xxx.xxx.xxx -p tcp --dport xxx -j REDIRECT --to-ports xxx" "$DELETE"

/jffs/scripts/dnsmasq.postconf
Code: 
#!/bin/sh
logger -t $(basename $0) "custom script started [$$]"
CONFIG=$1

/jffs/scripts/ipset-dnsmasq-update

if [ ! -f /tmp/dnsmasq_not_ready ]; then
  echo "### ipset redirections" >> "$CONFIG"
  echo "conf-file=/jffs/configs/dnsmasq.ipsetdns.conf" >> "$CONFIG"
fi

logger -t $(basename $0) "custom script ended [$$]"

/jffs/scripts/init-start
Code: 
#!/bin/sh
logger -t $(basename $0) "custom script started [$$]"

# dnsmasq delay loading of ipset configuration
touch /tmp/dnsmasq_not_ready

# load ipset modules
lsmod | grep "ipt_set" > /dev/null 2>&1 || \
(
  for module in ip_set ip_set_nethash ip_set_iphash ipt_set
  do
    insmod $module
  done
)

logger -t $(basename $0) "custom script ended [$$]"

/jffs/scripts/services-start
Code: 
#!/bin/sh
logger -t $(basename $0) "custom script started [$$]"

# restart dropbear with a custom configuration
/jffs/scripts/dropbear-start

# add cron jobs
#cru a id "minute(0-59) hour(0-23) day(1-31) month(1-12) weekday(0-6 with 0=Sunday) command"
cru a CheckSSHD              "*/5   *  *    *  *  /jffs/scripts/dropbear-start"

# start NWeb pixelserv if it is not already running
/bin/pidof nweb > /dev/null 2>&1 || (/jffs/bin/nweb 81 &)

# restore ipset tables
/jffs/scripts/ipset-restore

# dnsmasq delay loading of ipset configuration
(sleep 45 && (rm -f /tmp/dnsmasq_not_ready && service restart_dnsmasq)) &

logger -t $(basename $0) "custom script ended [$$]"
 
Last edited:
ASAT said:
This sometimes causes the creation of duplicate firewall rules
Click to expand...

I'm afraid not directly answering your question. 'cos I think it'll further increase the complexity in your setup. Seems to me from your log that if you put what's in nat-start into firewall-start i.e. abandon nat-start, you can avoid duplicate calls by the system.
 
kvic said:
put what's in nat-start into firewall-start
Click to expand...
That fixed it. Thank you, sir.

I may add a check at startup that only runs the nat-start logic from within firewall-start during startup. Once the router has gotten past the startup phase, it would use nat-start correctly.

In the meantime, I will set this option:
Administration -> System -> "Enable WAN down browser redirect notice" = NO

If this option is set to YES and the Internet connection goes down, the router:
1. flushes the NAT table
2. redirects port 80 to the "Internet is down" page

Then, when the Internet connection comes back up, the router:
1. flushes the NAT table, again
2. calls /jffs/scripts/nat-start
3. (does NOT call /jffs/scripts/firewall-start, and my NAT rules would have apparently "disappeared")

So it is important to use nat-start, as designed, ONLY when "Enable WAN down browser redirect notice" is YES. For now, I will set it to NO.
 
I dont understand all the code involved in this, all i can say is my ipset is empty, no populated data, the same as john reported.

how did you fix this john?

admin@RT-AC68U:/jffs/scripts# ipset --list
Name: Win10tracking
Type: iphash
References: 0
Header: hashsize: 1024 probes: 8 resize: 50
Members:

admin@RT-AC68U:/jffs/scripts# ipset --list Win10tracking
Name: Win10tracking
Type: iphash
References: 0
Header: hashsize: 1024 probes: 8 resize: 50
Members:
 
Chrysalis said:
I dont understand all the code involved in this, all i can say is my ipset is empty, no populated data, the same as john reported.

how did you fix this john?

admin@RT-AC68U:/jffs/scripts# ipset --list
Name: Win10tracking
Type: iphash
References: 0
Header: hashsize: 1024 probes: 8 resize: 50
Members:

admin@RT-AC68U:/jffs/scripts# ipset --list Win10tracking
Name: Win10tracking
Type: iphash
References: 0
Header: hashsize: 1024 probes: 8 resize: 50
Members:
Click to expand...

at first I missed that I have to install ipset-dns. then it dawned on me why we must have entware installed already. perhaps you missed that too?
 
john9527 said:
It's only populated when you access one of the sites in the tracking list.....try to open one in your browser, then check.
Click to expand...
ok gotcha, maybe add this to the guide OP?

anyway since I have the new firmware I did the guide on merlin's wiki instead now and confirm it works, this is very nice thanks.

Also I have no win10 machine running on my lan right now and a ip did add automatically so my win7 is doing some snooping :p (and I do have CEIP disabled).
 
cosmoxl said:
at first I missed that I have to install ipset-dns. then it dawned on me why we must have entware installed already. perhaps you missed that too?
Click to expand...

nah I have entware and did add the package. It was as john said I didnt try to access any of the hostnames.
 
Chrysalis said:
nah I have entware and did add the package. It was as john said I didnt try to access any of the hostnames.
Click to expand...

Note that with V14 of the fork (just posted for all), the function of ipset-dns is enabled in dnsmasq.....no entware package required. Use the 'newer than 378.55' link in the first post.

@ryzhov_al - Maybe you could edit your first post for me? Thanks.
 
john9527 said:
Note that with V14 of the fork (just posted for all), the function of ipset-dns is enabled in dnsmasq.....no entware package required. Use the 'newer than 378.55' link in the first post.
Click to expand...
yep I did. :)
 
I want Win10tracking to behave the same way when using TOR. It seems that after the packet has gone through NAT prerouting, it's no longer possible to match the destination IP against Win10tracking. Is it possible to do this without marking packets in the mangle prerouting table? That's how I did it. Is there a performance hit with marking the packets?

Example: Mark the packets to be blocked and apply a whitelist
Code: 
iptables -t mangle -I PREROUTING -m set ! --match-set whitelist dst,src -m set --match-set Win10tracking dst,src -j MARK --set-mark 0x1111

Example: Drop the marked packets
Code: 
iptables -I FORWARD -m mark --mark 0x1111 -j DROP

Example: Block Win10tracking IPs for devices on the network that are routed through a TOR transparent proxy
Code: 
iptables -t nat -I PREROUTING -i br0 -p tcp --syn -s 192.168.1.11 ! -d 192.168.1.0/24 -m mark ! --mark 0x1111 -m multiport --dports 80,443,995,587,993 -j REDIRECT --to-ports 9040
iptables -t nat -I PREROUTING -i br0 -p tcp --syn -s 192.168.1.12 ! -d 192.168.1.0/24 -m mark ! --mark 0x1111 -m multiport --dports 80,443,995,587,993 -j REDIRECT --to-ports 9040
iptables -t nat -I PREROUTING -i br0 -p tcp --syn -s 192.168.1.13 ! -d 192.168.1.0/24 -m mark ! --mark 0x1111 -m multiport --dports 80,443,995,587,993 -j REDIRECT --to-ports 9040
 
interesting, would the TOR issue also be an issue on other tunnels like VPN and 6to4?
 
You could look at the iptables packet counts to see that the packets are being dropped. You could also visit a website:
http://corp.sts.microsoft.com
OR
http://65.55.29.238

If the Microsoft Federation Services page comes, then your firewall is not blocking the Win10tracking IPs. Is the problem with dnsmasq, ipset-dns or the firewall rules?

Here's a check to verify that your setup is collecting IP addresses of the blocked sites:
Code: 
while read a;do nslookup $a;done <./Win10tracking.txt >out.txt

ipset -L Win10tracking

Once up and running for a while, it will return much IP addresses.
Code: 
Name: Win10tracking
Type: iphash
References: 1
Header: hashsize: 1024 probes: 8 resize: 50
Members:
2.16.4.112
2.16.4.139
2.16.4.152
2.16.4.168
2.16.63.10
2.16.63.25
2.16.63.59
2.17.235.20
2.19.182.238
2.19.186.73
2.21.243.51
2.22.22.209
2.22.22.219
12.129.210.71
23.102.21.4
23.206.108.111
23.206.39.87
23.40.4.243
23.43.39.4
23.62.99.25
23.66.24.154
23.78.53.200
23.99.10.11
31.13.92.2
37.252.162.10
37.252.162.101
37.252.162.103
37.252.162.104
37.252.162.12
37.252.162.125
37.252.162.135
37.252.162.136
37.252.162.137
37.252.162.138
37.252.162.139
37.252.162.140
37.252.162.141
37.252.162.144
37.252.162.147
37.252.162.15
37.252.162.152
37.252.162.155
37.252.162.158
37.252.162.187
37.252.162.189
37.252.162.19
37.252.162.191
37.252.162.199
37.252.162.2
37.252.162.20
37.252.162.200
37.252.162.201
37.252.162.202
37.252.162.203
37.252.162.205
37.252.162.206
37.252.162.208
37.252.162.209
37.252.162.210
37.252.162.211
37.252.162.212
37.252.162.213
37.252.162.216
37.252.162.217
37.252.162.218
37.252.162.219
37.252.162.22
37.252.162.220
37.252.162.221
37.252.162.222
37.252.162.224
37.252.162.226
37.252.162.227
37.252.162.228
37.252.162.230
37.252.162.232
37.252.162.234
37.252.162.237
37.252.162.238
37.252.162.239
37.252.162.24
37.252.162.240
37.252.162.241
37.252.162.242
37.252.162.243
37.252.162.244
37.252.162.251
37.252.162.252
37.252.162.253
37.252.162.29
37.252.162.3
37.252.162.30
37.252.162.35
37.252.162.36
37.252.162.4
37.252.162.41
37.252.162.49
37.252.162.5
37.252.162.50
37.252.162.51
37.252.162.52
37.252.162.53
37.252.162.58
37.252.162.59
37.252.162.6
37.252.162.61
37.252.162.64
37.252.162.67
37.252.162.68
37.252.162.69
37.252.162.7
37.252.162.70
37.252.162.72
37.252.162.75
37.252.162.77
37.252.162.78
37.252.162.79
37.252.162.8
37.252.162.81
37.252.162.82
37.252.162.83
37.252.162.84
37.252.162.87
37.252.162.89
37.252.162.9
37.252.162.90
37.252.162.91
37.252.162.95
37.252.162.96
37.252.162.98
37.252.163.1
37.252.163.100
37.252.163.101
37.252.163.102
37.252.163.103
37.252.163.104
37.252.163.105
37.252.163.106
37.252.163.107
37.252.163.108
37.252.163.109
37.252.163.110
37.252.163.111
37.252.163.112
37.252.163.113
37.252.163.114
37.252.163.115
37.252.163.119
37.252.163.152
37.252.163.153
37.252.163.154
37.252.163.155
37.252.163.156
37.252.163.162
37.252.163.163
37.252.163.164
37.252.163.165
37.252.163.167
37.252.163.168
37.252.163.172
37.252.163.177
37.252.163.183
37.252.163.184
37.252.163.194
37.252.163.195
37.252.163.196
37.252.163.199
37.252.163.203
37.252.163.204
37.252.163.205
37.252.163.206
37.252.163.207
37.252.163.208
37.252.163.209
37.252.163.210
37.252.163.211
37.252.163.212
37.252.163.213
37.252.163.214
37.252.163.215
37.252.163.216
37.252.163.217
37.252.163.218
37.252.163.219
37.252.163.220
37.252.163.221
37.252.163.222
37.252.163.223
37.252.163.224
37.252.163.225
37.252.163.226
37.252.163.227
37.252.163.228
37.252.163.229
37.252.163.232
37.252.163.233
37.252.163.234
37.252.163.235
37.252.163.236
37.252.163.237
37.252.163.238
37.252.163.239
37.252.163.240
37.252.163.241
37.252.163.242
37.252.163.243
37.252.163.244
37.252.163.3
37.252.163.4
37.252.163.5
37.252.163.6
37.252.163.69
37.252.163.7
37.252.163.70
37.252.163.71
37.252.163.72
37.252.163.73
37.252.163.74
37.252.163.75
37.252.163.76
37.252.163.77
37.252.163.78
37.252.163.79
37.252.163.8
37.252.163.80
37.252.163.81
37.252.163.82
37.252.163.83
37.252.163.84
37.252.163.85
37.252.163.86
37.252.163.87
37.252.163.88
37.252.163.89
37.252.163.9
37.252.163.90
37.252.163.91
37.252.163.92
37.252.163.93
37.252.163.94
37.252.163.95
37.252.163.96
37.252.163.97
37.252.163.98
37.252.163.99
37.252.170.1
37.252.170.10
37.252.170.100
37.252.170.102
37.252.170.104
37.252.170.105
37.252.170.106
37.252.170.107
37.252.170.108
37.252.170.109
37.252.170.11
37.252.170.110
37.252.170.111
37.252.170.112
37.252.170.113
37.252.170.114
37.252.170.115
37.252.170.116
37.252.170.117
37.252.170.118
37.252.170.119
37.252.170.120
37.252.170.121
37.252.170.122
37.252.170.123
37.252.170.124
37.252.170.125
37.252.170.126
37.252.170.13
37.252.170.135
37.252.170.137
37.252.170.138
37.252.170.140
37.252.170.141
37.252.170.142
37.252.170.143
37.252.170.144
37.252.170.145
37.252.170.146
37.252.170.148
37.252.170.15
37.252.170.150
37.252.170.151
37.252.170.155
37.252.170.157
37.252.170.158
37.252.170.159
37.252.170.16
37.252.170.165
37.252.170.166
37.252.170.167
37.252.170.168
37.252.170.169
37.252.170.17
37.252.170.175
37.252.170.18
37.252.170.180
37.252.170.19
37.252.170.20
37.252.170.21
37.252.170.22
37.252.170.23
37.252.170.24
37.252.170.26
37.252.170.27
37.252.170.28
37.252.170.29
37.252.170.30
37.252.170.31
37.252.170.39
37.252.170.4
37.252.170.40
37.252.170.41
37.252.170.42
37.252.170.43
37.252.170.44
37.252.170.45
37.252.170.46
37.252.170.47
37.252.170.48
37.252.170.49
37.252.170.5
37.252.170.60
37.252.170.61
37.252.170.63
37.252.170.64
37.252.170.65
37.252.170.66
37.252.170.68
37.252.170.69
37.252.170.71
37.252.170.72
37.252.170.77
37.252.170.79
37.252.170.8
37.252.170.80
37.252.170.81
37.252.170.82
37.252.170.86
37.252.170.87
37.252.170.88
37.252.170.89
37.252.170.9
37.252.170.90
37.252.170.91
37.252.170.92
37.252.170.94
37.252.170.95
37.252.170.97
37.252.170.98
37.252.170.99
46.33.68.17
46.33.68.65
52.0.227.108
52.6.18.63
62.115.249.137
62.115.249.144
64.233.167.148
64.233.167.149
64.233.187.148
64.233.187.149
64.4.11.42
64.4.54.22
64.4.54.254
64.4.54.32
64.4.6.100
65.52.100.11
65.52.100.7
65.52.100.9
65.52.100.91
65.52.100.92
65.52.100.93
65.52.100.94
65.52.108.153
65.54.226.187
65.55.108.23
65.55.252.43
65.55.252.63
65.55.252.71
65.55.252.92
65.55.252.93
65.55.29.238
65.55.32.30
65.55.39.10
65.55.44.109
66.119.144.190
68.67.128.143
68.67.128.52
68.67.129.102
68.67.129.111
68.67.129.119
68.67.129.120
68.67.129.189
68.67.129.193
68.67.152.10
68.67.152.101
68.67.152.102
68.67.152.106
68.67.152.107
68.67.152.123
68.67.152.124
68.67.152.127
68.67.152.128
68.67.152.134
68.67.152.199
68.67.152.211
68.67.152.231
68.67.152.232
68.67.152.235
68.67.152.237
68.67.152.29
68.67.152.30
68.67.152.32
68.67.152.53
68.67.152.62
68.67.152.66
68.67.152.70
68.67.152.71
68.67.152.72
68.67.152.73
68.67.152.74
68.67.152.75
68.67.152.76
68.67.152.77
68.67.152.78
68.67.152.80
68.67.152.81
68.67.152.83
68.67.152.84
68.67.152.86
68.67.152.9
68.67.152.93
68.67.152.96
68.67.153.149
68.67.153.154
68.67.153.159
68.67.153.160
68.67.153.162
68.67.153.163
68.67.153.18
68.67.153.180
68.67.153.181
68.67.153.182
68.67.153.203
68.67.153.204
68.67.153.21
68.67.153.210
68.67.153.212
68.67.153.23
68.67.153.238
68.67.153.246
68.67.153.249
68.67.153.255
68.67.153.26
68.67.153.29
68.67.153.30
68.67.153.33
68.67.153.34
68.67.153.43
68.67.153.58
68.67.176.11
68.67.176.124
68.67.176.127
68.67.176.13
68.67.176.132
68.67.176.133
68.67.176.134
68.67.176.135
68.67.176.16
68.67.176.21
68.67.176.24
68.67.176.34
68.67.176.36
68.67.176.54
68.67.176.62
68.67.176.67
68.67.176.9
74.125.130.148
74.125.130.149
74.125.200.148
74.125.200.149
74.125.68.148
74.125.68.149
77.67.11.19
77.67.11.67
80.231.240.217
80.231.240.234
80.252.91.24
80.252.91.25
80.252.91.41
82.199.80.141
82.199.80.142
82.199.80.143
84.53.146.32
84.53.146.83
88.221.14.115
88.221.14.128
88.221.14.138
88.221.14.144
88.221.14.146
88.221.14.176
88.221.14.193
88.221.15.19
88.221.15.33
92.122.122.138
92.122.122.146
92.122.122.147
92.122.122.155
92.122.122.160
92.122.122.161
92.123.224.52
92.123.224.68
94.245.121.176
94.245.121.177
94.245.121.178
94.245.121.179
95.101.112.58
95.101.112.8
104.86.110.50
104.93.5.50
104.93.82.168
104.93.82.176
104.93.82.179
104.93.82.185
104.93.82.19
104.93.82.203
104.93.82.26
104.93.82.8
111.221.29.177
111.221.29.253
111.221.29.254
131.107.113.238
131.107.255.255
131.253.14.76
131.253.40.44
134.170.115.60
134.170.185.70
134.170.53.29
134.170.53.30
134.170.58.118
134.170.58.121
134.170.58.123
134.170.58.189
157.55.129.21
157.55.240.220
157.56.121.89
157.56.122.82
157.56.149.250
157.56.23.91
157.56.91.77
168.63.108.233
172.227.56.60
172.229.180.108
173.194.112.123
173.194.112.124
173.194.112.27
173.194.112.28
173.194.113.123
173.194.113.124
173.194.113.91
173.194.113.92
173.194.120.123
173.194.120.124
173.194.120.155
173.194.120.156
173.194.126.123
173.194.126.124
173.194.126.59
173.194.126.60
173.194.126.91
173.194.126.92
173.194.40.155
173.194.40.156
173.194.45.59
173.194.45.60
173.194.45.91
173.194.45.92
173.223.120.207
184.24.201.63
184.27.34.161
184.51.148.122
184.51.148.130
191.232.139.253
191.232.139.254
192.67.191.126
195.215.247.10
195.215.247.17
195.215.247.24
195.215.247.80
195.215.247.9
202.177.203.124
202.79.210.121
203.213.73.16
203.213.73.24
203.213.73.8
204.79.197.197
204.79.197.200
204.79.197.201
204.79.197.203
204.79.197.204
204.79.197.206
204.79.197.208
204.79.197.209
204.79.197.210
204.79.197.211
207.46.194.10
207.46.194.14
207.46.194.25
207.46.194.8
207.46.223.94
207.68.166.254
216.58.196.198
216.58.196.38
216.58.196.70
216.58.197.102
216.58.208.230
216.58.208.70
216.58.210.70
216.58.211.102
216.58.221.102
216.58.221.134
216.58.221.230
216.58.221.38
216.58.221.70
 
Last edited:
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: 670 (members: 24, guests: 646)
Top