Client Classifying & AdGuard

#1

Hi,

I have a GL.inet GL-MV1000 (Marvell) and I am trying to use client classifying and individual options (link at end of this text) in conjunction with AdGuard however the client in question is still sending DNS requests through to AdGuard and not the specified DNS in the settings.

Any help would be muchly appreciated :smiley:

config dnsmasq
	option domainneeded '1'
	option boguspriv '1'
	option filterwin2k '0'
	option localise_queries '1'
	option rebind_protection '1'
	option rebind_localhost '1'
	option local '/lan/'
	option domain 'lan'
	option expandhosts '1'
	option nonegcache '0'
	option authoritative '1'
	option readethers '1'
	option leasefile '/tmp/dhcp.leases'
	option resolvfile '/tmp/resolv.conf.auto'
	option nonwildcard '1'
	option localservice '1'
	option noresolv '1'
	list server '127.0.0.1#3053'

config dhcp 'lan'
	option interface 'lan'
	option leasetime '12h'
	option force '1'
	option dhcpv6 'server'
	option ra 'server'
	option start '2'
	option limit '99'

config dhcp 'wan'
	option interface 'wan'
	option ignore '1'

config odhcpd 'odhcpd'
	option maindhcp '0'
	option leasefile '/tmp/hosts/odhcpd'
	option leasetrigger '/usr/sbin/odhcpd-update'
	option loglevel '4'

config domain 'localhost'
	option ip '192.168.0.1'
	option name 'the.internet'

config host
	option name 'TV'
	option dns '1'
	option mac 'XXXXXXXXXXX'
	option ip '192.168.0.2'
	option tag 'altdns'

config tag 'altdns'
	list dhcp_option '6,XXXXXXXXXXX'
#2

Any help would be appreciated :slight_smile:

#3

If you use Adguard home, it will take the priority to work as DNS. Otherwise it will not work.

#4

Yes and it appears the way they have AdGuard setup on the GL.iNet is that all queries are forwarded from localhost to AdGuard :frowning: so you can’t control individual clients in AdGuard.

I might just return the product to Amazon and get something else and load AdGuard on an OpenWRT router myself.

#5

check out this thread especially the comment below.

#6

(Although this may be a bug …) AdGuard Home can at least distinguish between its own local address (e.g. 192.168.8.1), localhost (127.0.0.1), and their ipv6 address.
By controlling the DNS server addresses that each client can connect to, I could do what I wanted.
Maybe, assigned to all addresses that AdGuard Home listens to.

Besides, with the latest update, AdGuard Home now has control over the client IDs that can be used for their filters, so it works well with other AdGuard products.

However, AdGuard Home is not a core feature of GL-iNet products. If you focus more on AdGuard filtering, your choice is definitely right :crossed_fingers: