What If LAN Devices, Printers, a NAS, or the Router Admin Page Are Unreachable?

LAN access problems usually mean a private subnet is being proxied, fake-ip is not excluding internal domains, TUN routes are capturing too much traffic, or the browser proxy is not bypassing local addresses.

View answerBack to category
  • Advanced Networking Scenarios
  • Troubleshooting
Short answer

LAN access problems usually occur because private subnets are proxied, fake-ip does not exclude local domains, TUN routing takes over too broadly, or the browser proxy does not bypass local addresses. Add DIRECT or exclusion rules for device domains and private subnets, then reload after updating fake-ip-filter; connection details should show DIRECT.

Which rule is taking over the private subnet or local domain?

Try the device IP and local domain once each. Check whether either hits a proxy, fake-ip, or TUN route, and record the actual private subnet.

  • Is the destination 192.168.x.x, 10.x.x.x, 172.16-31.x.x, or a local domain?
  • Do the rules include handling for LAN, private, DIRECT, or no-resolve?(See Rule-based Routing documentation)
  • Does fake-ip-filter include internal and local domains?(See DNS FAQ)
  • Is TUN routing also taking over the LAN subnet?

Make routers, NAS devices, and printers hit DIRECT again

  1. First add the router, printer, NAS, and local subnet to direct-routing rules
  2. Configure the browser proxy to bypass localhost and internal addresses
  3. Add lan, local, home.arpa, or the device vendor's local domain to fake-ip-filter
  4. In TUN scenarios, exclude LAN subnets and reload the configuration
  5. Use the connection list to confirm that internal traffic hits DIRECT

LAN devices generally do not need to use a proxy node

Proxying internal subnets by mistake can break casting, printing, file sharing, and the router admin page

Different clients may use different names for the LAN bypass setting