tailscale / tailscale/tailscale

Using exit node causes Parallels Desktop network subnet unreachable

Open
#7,454 5 comments 1 reaction 0 assignees View on GitHub
bug L2 Few OS-macos P2 Aggravating T5 Usability
Dominant language
Go
Stars
36.5k
Forks
3.2k
Avg merge
2d 3h
Merged PRs (30d)
123

Description

### What is the issue?

While using Tailscale along with Parallels Desktop, enabling exit node makes Parallels network interface (`bridge100`, `bridge101`, ...) subnet is not reachable from Host machine. Guest VM still had internet connection but couldn't ping each other(Host->Guest, Guest->Host).

Disabling exit node and restarting Parallels network interface through `ifconfig bridge101 down; ifconfig bridge101 up` resolves problem.

### Steps to reproduce

1. Start Parallels Desktop with Tailscale exit node disabled
2. Ping each other (Host->VM, VM->Host) through Host-Only Network interface `bridge101` succeded
3. Enable using Tailscale exit node
4. Step 2 failed. Also tried `traceroute` at this point but traiffic falls through Host network interface's gateway (public network), not a Tailscale network nor `bridge101` interface subnet.

### Are there any recent changes that introduced the issue?

I haven't used this combination, so I can't conclude software update could be possible issue.

### OS

macOS

### OS version

macOS Ventura 13.2.1

### Tailscale version

1.36.2 (App Store)

### Other software

## Firewalls
- LuLu 2.4.2

## Ad-Blockers
- AdGuard 2.9.2.1234

### Bug report

BUG-0a2c38da09ffdaf500b0f7174416f5772ab4fb18e7297f30e19c55beff1c6eb2-20230304065900Z-fae07145e379bdf9

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.