Home
Help
Search
Login
Register
OPNsense Forum
»
English Forums
»
General Discussion
»
AdGuardHome in a VM behind the FW
« previous
next »
Print
Pages: [
1
]
Author
Topic: AdGuardHome in a VM behind the FW (Read 1479 times)
marcanto
Newbie
Posts: 2
Karma: 0
AdGuardHome in a VM behind the FW
«
on:
January 28, 2022, 06:55:45 pm »
I run AdGuardHome in a VM on a server behind opnsense.
I tried to update the VM address as a DNS server under system | Setting | General - and got an error:
You can not assign a gateway to DNS server "192.168.*.*" which is on a directly connected network.
Is there a way to make this work ?
Logged
cookiemonster
Hero Member
Posts: 1823
Karma: 95
Re: AdGuardHome in a VM behind the FW
«
Reply #1 on:
January 28, 2022, 11:21:55 pm »
Can you explain a bit more what the setup is with ip addresses and ports. It isn't that clear at the moment.
Logged
marcanto
Newbie
Posts: 2
Karma: 0
Re: AdGuardHome in a VM behind the FW
«
Reply #2 on:
January 29, 2022, 10:41:03 am »
setup as attached.
I am tryng to make OPNsense use the truenas plugin as a dns filer for all the requests it get from users in the 192.168.7.* network
the plugin has its own ip and the truenas server has its own ip.
Logged
cookiemonster
Hero Member
Posts: 1823
Karma: 95
Re: AdGuardHome in a VM behind the FW
«
Reply #3 on:
January 30, 2022, 12:32:03 am »
It should work, there's no reason that ip can't be used. I had a similar setup when I had a VM with pihole. Maybe just a glitch or you had the incorrect gateway, try with "none".
Logged
Print
Pages: [
1
]
« previous
next »
OPNsense Forum
»
English Forums
»
General Discussion
»
AdGuardHome in a VM behind the FW