this post was submitted on 28 Nov 2025
10 points (100.0% liked)

Selfhosted

60482 readers
754 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:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details.

  8. AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post.

Resources:

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

Questions? DM the mods!

founded 3 years ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
ayyy@sh.itjust.works
curbstickle@anarchist.nexus
curbstickle_lw@lemmy.world
10
WireGuard LAN access fails when router VPN client is active (lemmy.blahaj.zone)
submitted 7 months ago* (last edited 7 months ago) by BonkTheAnnoyed@lemmy.blahaj.zone to c/selfhosted@lemmy.world
7 comments fedilink hide all child comments
 

I run WireGuard on my router to hit my LAN services (SAMBA, home assistant, etc) from afar.

But when I enable the VPN client on my router, I can no longer access LAN services over Wireshark. "Allow LAN access is set to 'true'" on the UI (Merlin).

Has anyone else run into this? Any ideas?

all 8 comments
sorted by: hot top controversial new old
[–] slazer2au@lemmy.world 7 points 7 months ago (2 children)

I must be thinking of the wrong Wireshark because the one I know of is a packet capture program not a VPN client/server.

[–] 0x0@lemmy.zip 7 points 7 months ago (1 children)

Maybe Wireguard?

[–] BonkTheAnnoyed@lemmy.blahaj.zone 5 points 7 months ago* (last edited 7 months ago)

Yep. Edited. Definitely autocorrect's fault, not my morning brain fog.

[–] BonkTheAnnoyed@lemmy.blahaj.zone 3 points 7 months ago (1 children)

No, actually you're right. I meant wire guard.

[–] slazer2au@lemmy.world 3 points 7 months ago

All good mate.

[–] non_burglar@lemmy.world 4 points 7 months ago* (last edited 7 months ago) (1 children)

You are asking the WG server to listen to incoming requests from outside your lan subnet, so it is ignoring VPN requests from that subnet.

There are two solutions to this:

  1. Add routing to your wireguard server instance to allow the VPN intermediary subnet to accept connections from your lan subnet or
  2. Allow your wireguard client to split-tunnel, so it can reach subnets that aren't reachable outside your WG tunnel.
[–] BonkTheAnnoyed@lemmy.blahaj.zone 1 points 7 months ago

Thank you, this is really helpful, a good place to start.