Xentrk
Part of the Furniture
Another thing to note that may prevent an IPSET list from being populated - routing the same domain to two different IPSET lists. This appears to be an issue but i want to run some more tests to be sure.
For example, say you created the IPSET list US-vpn1 and have pandora.com in it. Then, the next day, you run the script again, but create a new list called US-VPN and also use pandora.com in the list. When the domain is looked up, the IPSET list US-VPN does not get populated. The US-vpn1 list is listed first in dnsmasq. Looks like the match occurs there first. I've noticed this in some recent testing but need to revisit to validate.
For now, if you rename your IPSET lists, make sure to run the script with the original parameters along with the "del" parameter to remove the entry from /jffs/configs/dnsmasq.conf.add. Or, manually delete the entry from /jffs/configs/dnsmasq.conf.add using an editor.
For example, say you created the IPSET list US-vpn1 and have pandora.com in it. Then, the next day, you run the script again, but create a new list called US-VPN and also use pandora.com in the list. When the domain is looked up, the IPSET list US-VPN does not get populated. The US-vpn1 list is listed first in dnsmasq. Looks like the match occurs there first. I've noticed this in some recent testing but need to revisit to validate.
For now, if you rename your IPSET lists, make sure to run the script with the original parameters along with the "del" parameter to remove the entry from /jffs/configs/dnsmasq.conf.add. Or, manually delete the entry from /jffs/configs/dnsmasq.conf.add using an editor.