So I’m currently away from home and now I’m using the internet from another router.
My problem is that I can’t access my services because the default DNS from this router is 192.168.1.1 and the DNS that I use to access my services through wireguard is also 192.168.1.1
The wireguard service comes from my own router using Opnsense and I have setup unbound+Adguard DNS as 192.168.1.1 by default so I don’t know how can I solve this problem
I tried setting my computer to listen to 1.1.1.1 when connected to this wifi but when I enable my wireguard it still doesn’t connect to my services
I also tried enabling my Adguard to listen to All interfaces so it would enable the IP 10.50.50.0 as a DNS but I don’t know much about Opnsense so it also didn’t work when I changed the wireguard config file to listen to 10.50.50.0
My wireguard tunnel IP is set to 10.50.50.&& when connected to my router and the default IP when connected directly at home is the 192.168.1.&&
My phone can connect to the wireguard normally even when connected to this wifi
Does anyone had also this same problem as me could help me a little? Thank you.
Sorry for the bad english
[Conclusion] i went looking into the wireguard subreddit for a smillar problem as mine and found that if the outside router uses 192.168.1.1 as the default gateway & dns when trying to connect to my tunnel ip the browser will search on the main router instead of my wireguard tunnel. I’m going to need to change my ip addresses to another ip instead of the default 192.168
Post
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.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world
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
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.