AdGuard: Port 5310 ist closed -- why? #7416
Unanswered
white-rabbit07
asked this question in
Q&A
Replies: 1 comment
-
hm -- is it really that simple: just a missing firewall-rule like this one? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi.
I don't know if this is a "bug or a feature" but I have a problem using AdGuard on Port 5310.
As you can see here, AdGuard is installed an listening on port 5310 in these subnets:
Next thing I tried was a nmap-test if port 5310 is open (from my management network):

-- worked.
After that I tried to use AdGuard with dig -- worked:

And then the problems began:

The same test from a client in my WiFi-Subnet showed that the port is closed. Why?
The last test was a "regular" DNS-Test with Wireshark on port 53 which was no problem:

And finally the DNS-Request on port 5310 with Wireshark:

The Client-IP is registered in the AdGuard-WebUI. So: What's the problem here?
Thanks for any hint.
AdGuard Home Version: v0.107.54 -- running as a plugin on OPNSense 24.7.5_3
Beta Was this translation helpful? Give feedback.
All reactions