Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Wireguard LAN ERR_TIMED_OUT

    Scheduled Pinned Locked Moved WireGuard
    1 Posts 1 Posters 186 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • A
      Andan60
      last edited by

      Goal: Create 3 WG VPNs with multiple peers.
      WG_NETALL - Access all of LAB_LAN & pass internet through pfBlockerNG - 192.168.21.0
      WG_WANDNS - Pass internet through pfBlockerNG, no access to LANs
      WG_LANCAP - Access only LAN, does not pass internet

      I am currently working on WG_NETALL and only have my phone (WiFi is off) as the first peer. While I am able to have a connection to the VPN and access the internet, I cannot access the LAB_LAN (192.168.11.0) subnet.

      When attempting to access pfSense at 192.168.11.1, I get an error message
      This site can't be reached, took too long to respond, ERR_TIMED_OUT, same behavior when trying to access my NAS.

      pfBlockerNG sorta works on the VPN, it too gives an ERR_TIMED_OUT vs the normal NET::ERR_CERT_AUTHORITY_INVALID.

      I'm at a lost on what I am supposed to do, I have read I need rules on both LAB_LAN & WG_NETALL in order to have access. I have also messed with the Allowed IPs to gain access even though 0.0.0.0/0 should be allow all.

      Configs
      Note: pfSense is running inside a VM on Proxmox, cable modem is plugged into a passthrough NIC to the VM.
      NAT Outbound.png
      WG Firewall Rules.png WAN Firewall Rules.png WG_NETALL Firewall Rules.png WG Tunnel.png WG_Peers.png
      WG Pixel Interface.jpg

      1 Reply Last reply Reply Quote 0
      • First post
        Last post
      Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.