Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login
    Introducing Netgate Nexus: Multi-Instance Management at Your Fingertips.

    Firewalling and VPN 101

    Scheduled Pinned Locked Moved Firewalling
    4 Posts 2 Posters 1.3k 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 Offline
      awsiemieniec
      last edited by

      pfSense 2.1.5 amd64
      OpenVPN site-to-site between four locations - A: server, B, C, D: client

      I can ping from all of the devices on the client networks to the pfsense server LAN interface but nothing past that - I can't ping/communicate with anything on the LAN subnet.  I've done this a few times and it always works so I know I'm missing something real simple here but I can't see it.

      The VPNs connect just fine but I can't get on the LAN of each client from the server and vice versa.

      Server:
      Firewall/WAN Rules:
      [empty], IPv4UDP, <public 1="" ip="" of="" remote="" office="">, *, WAN Address, 1194, *, None, [empty]
      [empty], IPv4UDP, <public 2="" ip="" of="" remote="" office="">, *, WAN Address, 1195, *, None, [empty]
      [empty], IPv4UDP, <public 3="" ip="" of="" remote="" office="">, *, WAN Address, 1196, *, None, [empty]

      Firewall/LAN Rules:
      [empty], IPv4 *, *, *, *, *, [empty]

      Firewall/OpenVPN Rules:
      [empty], IPv4 *, *, *, *, *, [empty]

      Client B, C, D
      Firewall/WAN Rules:
      (rule for remote administration)

      Firewall/LAN Rules:
      [empty], IPv4 *, *, *, *, *, [empty]

      Firewall/OpenVPN Rules:
      [empty], IPv4 *, *, *, *, *, [empty]

      So as you can see the rules are pretty loose at this point.

      Server A:
      LAN: 192.168.1.0/24

      Client B:
      LAN: 192.168.4.0/24
      Tunnel network: 172.16.1.0/30

      Client C:
      LAN: 192.168.8.0/24
      Tunnel network: 172.16.2.0/30

      Client D:
      LAN: 192.168.6.0/24
      Tunnel network: 172.16.3.0/30

      Any ideas?

      thank you.</public></public></public>

      1 Reply Last reply Reply Quote 0
      • DerelictD Offline
        Derelict LAYER 8 Netgate
        last edited by

        Are you positive you're not seeing a software firewall (think windows firewall) on the client that thinks the remote networks are just that and not allowing traffic in, resulting in no response?

        Chattanooga, Tennessee, USA
        A comprehensive network diagram is worth 10,000 words and 15 conference calls.
        DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
        Do Not Chat For Help! NO_WAN_EGRESS(TM)

        1 Reply Last reply Reply Quote 0
        • A Offline
          awsiemieniec
          last edited by

          I'll remote in and make sure all the Windows firewalls are stopped.  thanks for the idea.

          1 Reply Last reply Reply Quote 0
          • A Offline
            awsiemieniec
            last edited by

            that darn Windows firewall.  Gets me every time!

            Thanks, that was the problem.  After I ran "netsh advfirewall set allprofiles state off" command on a few machines on different subnets, they were able to talk to each other.

            thank you for your suggestion; it was spot on.

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