# Networking: VPN is connected but I can't reach the internal network — missing routes, split tunnel or overlapping subnets

**Code:** `VPN connected but internal subnets unreachable` · **Category:** Networking · **Seen on:** Linux, Windows, Networking

The tunnel is up, but traffic for the office/VPC subnets isn't sent through it or comes back the wrong way.

## Meaning

Check the client routing table for the remote subnet (`ip route` / `route print`), the server's pushed routes or AllowedIPs, and whether your home LAN uses the same subnet (e.g. both 192.168.1.0/24). Fix by adding the route, changing the local subnet, or correcting split-tunnel settings and return routes on the remote side.

## Common causes

- Remote subnet not in AllowedIPs / pushed routes
- Home and office subnets overlap
- Split tunnel excludes the destination
- No return route on the remote router
- Firewall on the VPN server blocks the forwarded traffic

## Quick fix

1. Show routes: `ip route` / `route print` for the remote subnet
2. Change the local LAN subnet if it overlaps
3. Add AllowedIPs/routes and ensure IP forwarding on the server

## Detailed fix by platform

### Linux

1. 

```bash
ip route get 10.20.0.15
sudo wg show   # AllowedIPs should contain 10.20.0.0/16
sysctl net.ipv4.ip_forward
```


## How to diagnose

1. **Route** — Present via tunnel?
2. **Subnets** — Overlapping?
3. **Return route** — Exists?

---
Source: [WhatIsMyError](https://whatismyerror.com/errors/networking/vpn-connected-cannot-reach-internal-subnets)