10.50.50.0 is not a valid IP address in most configurations. Have you tried 10.50.50.1?
this post was submitted on 28 Sep 2023
23 points (96.0% liked)
Selfhosted
39937 readers
343 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 1 year ago
MODERATORS
I didn't know that, in Adguard > Setup guide > configure your devices. Since I selected to listen to All interfaces there are lots of IP addresses so I just copied the IP from my wireguard interface like this.
5353 is not the port that most devices use for dns,.that would be port 53, so if it's not listening there the no connection would be made
Yes it's because I use unbound and Adguard on opnsense, Adguard uses 5353 and unbound uses 53, so in opnsense I went to Services > Unbound DNS > query forwarding and added the IP 10.50.50.0:5353 but even doing that didn't work on my wireguard config file.
Thinking more into it the reason that It didn't work was because unbound is the primary DNS and Adguard would become the secondary DNS, if there was a way to create another IP for unbound I think my problem would be solved, but Im still learning about opnsense so I don't know how would I do it.
ah ok so I would think you would want to set that to 127.0.0.1:5353 if it is on the same machine as the router an just use the router as the DNS server in wireguard
that would have traffick like this:
client > 192.168.1.1(router) dns server > loopback to adguard
thank you for the support, i was able to make Unbound listen to 10.50.50.0 as a dns but when i tried to access me services on 192.168.1.$$ the same problem occured. i also found another simillar post that had the same problem as mine so i now know it will not work, but thanks for the help
Immediate workaround - use your phone's config. I would then try to build another config for the phone based on a working one.
But the problem is the DNS, I think the phone isn't as picky as the computer when connecting to wireguard that why it works, I will try doing that but I don't think that's the problem
If you genuinely suspect the computer - try checking routing tables. Although that's impossible to help you with as the environment would be unfamiliar.