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

    1 WAN interface, 3 LAN interfaces, OpenVPN allow communication to all networks

    Scheduled Pinned Locked Moved General pfSense Questions
    44 Posts 4 Posters 2.7k 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.
    • stephenw10S
      stephenw10 Netgate Administrator
      last edited by

      The states are correct but there is no translation. Did you add an appropriate OBN rule there too?

      J 1 Reply Last reply Reply Quote 0
      • J
        jg8000 @stephenw10
        last edited by

        @stephenw10

        I see those states no matter if the OBN is there or not.

        1 Reply Last reply Reply Quote 0
        • stephenw10S
          stephenw10 Netgate Administrator
          last edited by

          What OBN rule are you setting there?

          J 1 Reply Last reply Reply Quote 0
          • J
            jg8000 @stephenw10
            last edited by

            @stephenw10 Screenshot 2024-05-24 at 8.36.46 AM.png

            1 Reply Last reply Reply Quote 0
            • stephenw10S
              stephenw10 Netgate Administrator
              last edited by

              Is that destination the address or subnet? It needs to be the OPT2 subnet there to match.

              J 1 Reply Last reply Reply Quote 0
              • J
                jg8000 @stephenw10
                last edited by

                @stephenw10

                It's the subnet. Does I need this Outbound rule when setting the OPT2 (192.168.3.0/24) as local networks in the OpenVPN config?

                Screenshot 2024-05-24 at 8.50.02 AM.png .

                1 Reply Last reply Reply Quote 0
                • stephenw10S
                  stephenw10 Netgate Administrator
                  last edited by

                  Yes you still need the rule because hosts in the OPT2 subnet will block access from the VPN subnet directly.

                  That rule should match if the subnets are correct.

                  J 1 Reply Last reply Reply Quote 0
                  • J
                    jg8000 @stephenw10
                    last edited by

                    @stephenw10

                    Is there a way to just have the vpn clients land on the OPT2 subnet? Would that solve the problem?

                    1 Reply Last reply Reply Quote 0
                    • stephenw10S
                      stephenw10 Netgate Administrator
                      last edited by

                      Yes, you can setup the VPN as TAP and bridge the interfaces. But that will only work for one interface and you have 3. And it introduces a bunch of other things you don't want so I wouldn't recommend it.

                      Adding an OBN rule that matches will allow this to work. The best solution is to just allow it on the hosts though.

                      Make sure the rules are actually loading in Status > Filter Reload. Make sure it returns without errors.

                      J 1 Reply Last reply Reply Quote 0
                      • J
                        jg8000 @stephenw10
                        last edited by

                        @stephenw10

                        Ok, I'm confused now.

                        Looks as if rules are being loaded without error.

                        This is my Outbound rule

                        Screenshot 2024-05-24 at 10.34.42 AM.png

                        1 Reply Last reply Reply Quote 0
                        • stephenw10S
                          stephenw10 Netgate Administrator
                          last edited by

                          Yet you still see the states with no NAT applied?

                          J 1 Reply Last reply Reply Quote 0
                          • J
                            jg8000 @stephenw10
                            last edited by

                            @stephenw10

                            I still can’t get it to work on my test setup, but I was able to solve the production issue.

                            It was the Cisco switches breaking comms between the devices and the firewall. No fix yet, other than to use a dumb switch. The traffic flowed just fine right away, I was able to provision the nodes with no issue.

                            I’m still seeing some weird timeouts with the VPN, could be a timeout issue, not sure

                            Thanks so much for all of your help

                            1 Reply Last reply Reply Quote 0
                            • stephenw10S
                              stephenw10 Netgate Administrator
                              last edited by

                              Ah, well that's a much better solution. Adding NAT in there is always a workaround.

                              That NAT looks like it should match and be applied though.

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