this post was submitted on 29 Dec 2023
46 points (96.0% liked)

Selfhosted

39224 readers
392 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
46
[solved] WireGuard VPN IP Issue (lemmy.self-hosted.site)
submitted 8 months ago* (last edited 8 months ago) by [email protected] to c/[email protected]
 

I tried debugging this issue for hours now but I'm out of ideas. I'm running WireGuard on my OPNsense firewall. It worked flawlessly for about a year but now I've gotten a really strange issue.

Here is the Client config: Client

As you can see, the Client got assigned the IP 10.10.10.11/32

I can ping this IP and the Client can access all Server in the network when connected with the VPN.

BUT when it connects to hosts in the LAN, it doesn't use it's assigned 10.10.10.11 IP but the public IP of the OPNsense firewall instead.

This also doesn't happen every time, but most of the time. I assume that it's perhaps a ARP issue, but I don't know why the OPNsense firewall sends its public IP (WireGuard Endpoint IP) instead of the Clients assigned IP at all.

The IP the Client should use in the LAN (virtual VPN IP): virtual IP

The IP which the Client actually uses (Endpoint IP): Endpint IP

Every help would be greatly appreciated!


EDIT: I removed and re-added the peers in OPNsense and it works again, at least for now. Maybe something broke during an update(?). I will report back if this already fixed the issue (the problem can sometimes be hard to replicate)

EDIT 2: The issue reappeared. But I noticed, that I now have the problem only with Gecko based browsers, chromium works fine (tested on Android).

EDIT 3: The issue only appeared with Gecko based browsers because mine are configured to use some public DOH DNS, which resolved my internal host FQDNs to public IPs, not private ones from the LAN

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 2 points 8 months ago (2 children)

Change your allowed IPs config to 0.0.0.0/0

[–] [email protected] 2 points 8 months ago

Wouldn't this tunnel everything? I just want 10.10.10.0/24 and 10.0.0.0/24 (VPN and LAN IP range to get tunneled). I also don't know how this would mitigate this issue

[–] [email protected] 1 points 8 months ago (1 children)

Thanks for the pointer, it seems it's an DNS issue after all (IT'S ALWAYS DNS). Routing all traffic through the tunnel forces the Clients to use the DNS server of the LAN. Without, my internal websites (which use a public domain namespace) are sometimes resolved with a public DNS. So the browser doesn't request test.home.network (10.0.0.100) but test.home.network (1.19.72.59).

[–] [email protected] 1 points 8 months ago

Glad you figured it out. I've also run into issues with Firefox using the wrong DNS.