Wireshark LAN access fails when router VPN client is active

Submitted ⁨⁨4⁩ ⁨weeks⁩ ago⁩ by ⁨BonkTheAnnoyed@lemmy.blahaj.zone⁩ to ⁨selfhosted@lemmy.world⁩

I run Wireshark 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?

source

Comments

Sort:hotnew top

slazer2au@lemmy.world ⁨4⁩ ⁨weeks⁩ ago
I must be thinking of the wrong Wireshark because the one I know of is a packet capture program not a VPN client/server.

source
- 0x0@lemmy.zip ⁨4⁩ ⁨weeks⁩ ago
  Maybe Wireguard?
  
  source
  - BonkTheAnnoyed@lemmy.blahaj.zone ⁨4⁩ ⁨weeks⁩ ago
    Yep. Edited. Definitely autocorrect’s fault, noty morning brain fog.
    
    source
- BonkTheAnnoyed@lemmy.blahaj.zone ⁨4⁩ ⁨weeks⁩ ago
  No, actually you’re right. I meant wire guard.
  
  source
  - slazer2au@lemmy.world ⁨4⁩ ⁨weeks⁩ ago
    All good mate.
    
    source
non_burglar@lemmy.world ⁨4⁩ ⁨weeks⁩ ago
There are two solutions to this:

Add routing to your wireguard server instance to allow the VPN intermediary subnet to reach your lan subnet or

Allow your wireguard client to split-tunnel, so it can reach subnets that aren’t reachable outside your WG tunnel.
source
- BonkTheAnnoyed@lemmy.blahaj.zone ⁨4⁩ ⁨weeks⁩ ago
  Thank you, this is really helpful, a good place to start.
  
  source