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

    Routing Setup

    Scheduled Pinned Locked Moved Routing and Multi WAN
    22 Posts 3 Posters 5.0k 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.
    • M
      medicshelley
      last edited by

      My default router is not the pfsense box Im guessing this might be part of the issue as well

      1 Reply Last reply Reply Quote 0
      • P
        podilarius
        last edited by

        In the VPN rule in firewalling, it will not be the WAN net. It is going to be the remote  private subnet. I would do a source any until you know the vpn config is sound.

        1 Reply Last reply Reply Quote 0
        • P
          podilarius
          last edited by

          @medicshelley:

          My default router is not the pfsense box Im guessing this might be part of the issue as well

          It could be, so you would need to add the route to the remote subnet in your default router to the pfsense box.

          1 Reply Last reply Reply Quote 0
          • M
            medicshelley
            last edited by

            Could I make the default router the pfsense box for those 10.87.3/100 lans?

            1 Reply Last reply Reply Quote 0
            • P
              podilarius
              last edited by

              If the traffic doesn't have to go in another direction, yes.

              1 Reply Last reply Reply Quote 0
              • M
                medicshelley
                last edited by

                I was just playing around and turned off the firewall completely once I did that I was able to ping the opposite ends of the tunnel from both sides from the webgui. I wasn't able to reach the local subs on either end. So this just has to be a routing/rules issue

                1 Reply Last reply Reply Quote 0
                • P
                  podilarius
                  last edited by

                  So far that is what it sounds like … but the rule you have is not correct either .. WAN net is only the subnet that you WAN is on and not the internet.

                  1 Reply Last reply Reply Quote 0
                  • H
                    heper
                    last edited by

                    also … maybe ... perhaps ... do not use port 443, possibly the pfsense webgui httpd is allready bound to it.

                    1 Reply Last reply Reply Quote 0
                    • M
                      medicshelley
                      last edited by

                      I restarted and am now able to ping across to the other sides vpn tunnel and front end of the other lan from the webgui but am unable to ping from a station on those lan's.

                      1 Reply Last reply Reply Quote 0
                      • P
                        podilarius
                        last edited by

                        Did you change the OpenVPN firewall allow rule on both sides? Try a reboot on both sides after that. Also check your routing on the remote site to make sure that is not an issue.

                        1 Reply Last reply Reply Quote 0
                        • M
                          medicshelley
                          last edited by

                          I'm rebooting on both ends now here are my current rules on both the server and client

                          lanrules.png
                          lanrules.png_thumb
                          vpnrules.png
                          vpnrules.png_thumb
                          wanrules.png
                          wanrules.png_thumb

                          1 Reply Last reply Reply Quote 0
                          • P
                            podilarius
                            last edited by

                            Your LAN rule is incorrect. Again WAN address or WAN subnet is not the internet nor either side of the tunnel. Change the source to be any to any on any port to start with. After you have made sure that the connection is working and the routing is correct, then you can limit your rules if you like. Just make sure that you are wary of what you are blocking and please make use of aliases to help you create rules.

                            1 Reply Last reply Reply Quote 0
                            • M
                              medicshelley
                              last edited by

                              Thanks by altering that rule I am now able to ping everything and anything on the lan side.

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