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

    Bypass VPN VLAN to external IP?

    Scheduled Pinned Locked Moved General pfSense Questions
    27 Posts 3 Posters 838 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.
    • S
      SubSeven @stephenw10
      last edited by

      @stephenw10 Those look empty. I'm going to restart pfSense to see if that does anything and I'll also restart the Win PC and the Linux server.

      e09265b7-d3de-4587-8129-e3cfabc332d9-image.png

      1 Reply Last reply Reply Quote 1
      • S
        SubSeven @stephenw10
        last edited by

        @stephenw10 I powered all 3 down, started pfSense back up, then Linux server, and then the Win 10 PC but the good old "restart your computer" trick didn't help :)

        I tried the ping and that seems to work:
        b8f6f804-d384-4ef2-8ea0-a5d555587027-image.png

        At the same time I was doing that I checked the states again and saw an entry for ...99.106:
        64929a20-d41a-474f-ba29-98ae96218782-image.png

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

          Ok, so that is translating as expected.

          One thing I see is that pfSense has two IP addresses in that subnet, 192.168.99.99 and 192.168.99.200. Which of those is the WAN address?

          S 3 Replies Last reply Reply Quote 0
          • S
            SubSeven @stephenw10
            last edited by

            @stephenw10 192.168.99.99 is the gateway of the parent router, it is part of my old / original network which I want to eventually get rid of. That one is running OpnSense.

            c430f4fb-8bd8-4d61-8445-00e40a445452-image.png

            I access it from what I labeled as test PC (...99.111):
            b800ba5c-165b-4518-9845-3f4f6573e9ad-image.png

            To get to the pfSense PC we've been talking about, I would go to 192.168.99.200 so that tells me that is the WAN IP.

            1 Reply Last reply Reply Quote 0
            • S
              SubSeven @stephenw10
              last edited by SubSeven

              @stephenw10 I also wanted to share the details of the outbound NAT that is used for the VPN in case there is something in there.

              84e39584-4a2a-4ed3-b1fd-bd00cc856d67-image.png

              851ad1dd-93c8-4596-bb91-2c5e44ddbed5-image.png

              1 Reply Last reply Reply Quote 0
              • S
                SubSeven @stephenw10
                last edited by

                @stephenw10 Just in case this is helpful:

                b7f96bd3-267e-48f4-ac76-4d475e1219d8-image.png

                58da8b90-b9e7-465c-a95c-bd104f8f84d4-image.png

                4b5f2a15-c5a4-46e5-a87d-594304b7f8c7-image.png

                b39e5dc7-78c6-452f-9bab-9a4f984e1802-image.png

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

                  Ah I see. Yes that all looks OK. That outbound NAT rule is not in play here since traffic isn't leaving via the VPN.

                  It feels like the incoming rule on OPT9 is preventing it open the WAN state somehow. If you disable the policy routing rule and just pass traffic there without a gateway does it work?

                  S 1 Reply Last reply Reply Quote 0
                  • S
                    SubSeven @stephenw10
                    last edited by

                    @stephenw10

                    I "grayed that out", I'm pretty sure that's what you mean.

                    5b6cea88-0b81-4ad3-90f9-d95996b3ba67-image.png

                    I was still having no luck and I tried something else which is another PC, coming in from VLAN20 and I put in the following rule:

                    aea82cfb-8d83-45a5-a02b-410b25c20db7-image.png

                    However I'm not able to access the internet, or ...99.99, or 99.106 and VLAN20 should have nothing to do with the VPN. Granted I should have tried this much sooner. I must have something else going on and I just feel awful for taking up your time. I still think it's related to pfSense and not something external like switches or parent router. I'm just going to keep trying stuff and if nothing works I will in the end reinstall pfSense from scratch, if it comes to that but there are lots of things I will try before that. Once I get it to work, I will let you know about it.
                    If there is anything you would like me to try by all means I'd be happy to but I don't want to take up anymore of your time and let me just say that I appreciate all your help so much!

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

                      Same symptoms? No outbound state at all?

                      1 Reply Last reply Reply Quote 0
                      • V
                        viragomann @SubSeven
                        last edited by

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