Can not access local IP when connected to exit node

SUPPORT QUESTIONS
1

So, I’ve setup the exit-node destination on windows machine with --exit-node-allow-lan-access=true and it works well… until I try to connect with ssh to other machine on the same network.

it stuck on connecting…

debug1: Connecting to 172.27.164.60

and eventually timed out, but it didn’t happened after I quit from exit-node.

I assume the IP I was trying to connect is in the same network because online IP lookup service says it’s private IP.

but if the host are indeed in the same network, why it seems it come from different network? here’s the partial output of ipconfig

Wireless LAN adapter Wi-Fi:

   Connection-specific DNS Suffix  . : <redacted-domain-name>
   Link-local IPv6 Address . . . . . : <redacted>
   IPv4 Address. . . . . . . . . . . : 10.87.136.37
   Subnet Mask . . . . . . . . . . . : 255.255.252.0
   Default Gateway . . . . . . . . . : 10.87.136.1

I come from web developer background and not a network engineer, so I might be misunderstanding the whole thing since I’m new in this network related stuff, so please correct me if my assumption is wrong.

  • is the only way to fix this situation is by quit from exit-node each time I need to ssh to 172.27.164.60?
  • any explanation to help me better understand the situation would be very appreciated!

Thanks in advance for your time and patient.

Tailscale client version 1.74.0
operating system & version:

OS Name:                   Microsoft Windows 11 Home Single Language
OS Version:                10.0.22631 N/A Build 22631

Tailscale exit-node version 1.74.1
operating system & version:

$ uname -a
Linux server 6.10.7-arch1-1 #1 SMP PREEMPT_DYNAMIC Thu, 29 Aug 2024 16:48:57 +0000 x86_64 GNU/Linux