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

    VLAN OpenVPN issues

    Scheduled Pinned Locked Moved General pfSense Questions
    6 Posts 2 Posters 586 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.
    • J
      jTJin
      last edited by

      Good Morning,

      I've just rebuilt my network to include VLANs, mainly to learn, with the end result being of isolating all of my IoT devices.

      So far I think I've muddled through enough guides to gain a reasonable idea of what I am doing. I am however stumped one one thing (so far).

      When I am on the WiFi (and therefore VLAN 10) I can get internet etc etc and do everything I expect. Except, when I try and connect OpenVPN to a different pfSense box.
      I've had this second box up and working for years, with an OpenVPN server. When I am not on my internet I can connect and I have full internet access and access to the LAN
      When I connect from inside the VLAN however the connection completes, I get issued an IP address. But I can't access the internet or the LAN. Everything just times out.
      I am guessing it is a routing issue to do with my VLANs, but not sure where to start

      Kind Regards

      1 Reply Last reply Reply Quote 0
      • johnpozJ
        johnpoz LAYER 8 Global Moderator
        last edited by

        And this other vpn server your connecting too... What is the tunnel network used? Does it overlap your new vlan network? What is this remote network your trying to access does it overlap your new vlan 10 network?

        An intelligent man is sometimes forced to be drunk to spend time with his fools
        If you get confused: Listen to the Music Play
        Please don't Chat/PM me for help, unless mod related
        SG-4860 24.11 | Lab VMs 2.8, 24.11

        1 Reply Last reply Reply Quote 0
        • J
          jTJin
          last edited by

          If I understand the question correctly (and please excuse me if I dont) I think you might have hit the nail on the head.

          VLAN 10 is a network of 192.168.10.0/24... and now I think about ti when you connect to the tunnel you are issued a 192.168.10.x address. Will this give me the issues I am having?

          1 Reply Last reply Reply Quote 0
          • johnpozJ
            johnpoz LAYER 8 Global Moderator
            last edited by

            You can not have tunnel network or remote network that overlaps your current network.

            If your on 192.168.10.0/24 and the tunnel network is the same? Or overlaps say 192.168.0.0/16 or the remote network again is the same as your local or overlaps... Then yeah your going to have a bad day ;)

            An intelligent man is sometimes forced to be drunk to spend time with his fools
            If you get confused: Listen to the Music Play
            Please don't Chat/PM me for help, unless mod related
            SG-4860 24.11 | Lab VMs 2.8, 24.11

            J 1 Reply Last reply Reply Quote 0
            • J
              jTJin @johnpoz
              last edited by

              @johnpoz
              Amazing, thank you. Makes complete sense but one of those things I was chasing my own tail on. Moved the tunnel network to 192.168.3.0/24. And unsurprisingly it now connects fine on the VLAN and works as intended.

              1 Reply Last reply Reply Quote 0
              • johnpozJ
                johnpoz LAYER 8 Global Moderator
                last edited by johnpoz

                Good to hear - yeah this is why its a good idea to use non common networks for tunnel and your local networks.. For example 192.168.0 and 192.168.1 are very common!

                Good tunnel networks are in the 17.16/12 rfc1918 space... Like say 172.29.14/24 or something ;)

                Many hot spots that you might be at where you want to go home so using common networks locally.. Can cause you problems from your remote location when your wanting to vpn home... So good to use odd networks at home too.. I use 192.168.9/24 for my normal lan, have yet to run into an issue with that.. But yeah you never know what network you might be on ;)

                Also why good to not use large networks.. When you see someone using 192.168/16 or 10/8 they prob going to have issues trying to vpn out or in ;)

                An intelligent man is sometimes forced to be drunk to spend time with his fools
                If you get confused: Listen to the Music Play
                Please don't Chat/PM me for help, unless mod related
                SG-4860 24.11 | Lab VMs 2.8, 24.11

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