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

    connected but cant access vpn lan after upgrade to 2.4.4 p1

    Scheduled Pinned Locked Moved OpenVPN
    35 Posts 6 Posters 3.6k 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
      ariban99
      last edited by

      Hi
      thank you for your response.
      here are the screenshots
      server for 10.0.1.0 (WORKING ONE)
      0_1544537505831_screencapture-192-168-1-1-vpn_openvpn_server-php-2018-12-11-06_08_49.png
      here is the server for 10.0.3.0 (NOT WORKING ANYMORE)
      0_1544537561734_screencapture-192-168-1-1-vpn_openvpn_server-php-2018-12-11-06_09_04.png

      here is the client side for the working one 10.0.1.0
      0_1544537613320_screencapture-192-168-2-1-vpn_openvpn_client-php-2018-12-11-06_06_23.png

      1 Reply Last reply Reply Quote 0
      • A
        ariban99
        last edited by

        this one shows the status of the openvpn that is NOT working, it shows connected and UP0_1544537742411_screencapture-192-168-3-1-status_openvpn-php-2018-12-11-06_15_11.png

        1 Reply Last reply Reply Quote 0
        • A
          ariban99
          last edited by

          and here is the client side for the one NOT working 10.0.3.0/24
          link text
          somehow i cant upload this screenshot, every time it gives me an error, so i uploaded it to my google drive as a screenshot
          thank you

          N 1 Reply Last reply Reply Quote 0
          • N
            netblues @ariban99
            last edited by

            @ariban99 try removing 192.168.3
            .0 from remote networks on the working config.
            Remember to clear states and restart openvpn.

            1 Reply Last reply Reply Quote 0
            • A
              ariban99
              last edited by

              Hi
              thank you. that works now.
              however, now i can not access between the 2 remote locations. so from each remote i can access the main server. but between remote locations, i cant access each other.
              is there a way to talk to the 2 remote locations. so in this example
              from 192.168.3.0 (tunnel 10.0.3.0)
              to 192.168.2.0 (tunnel 10.0.1.0)

              thank you

              1 Reply Last reply Reply Quote 0
              • N
                netblues
                last edited by

                Assign ovpn interfaces ( if you havent done already) and policy route among the two is probably the way to go.
                Put roules on openvpn tab sending traffic with specific source and destination to relevant openvpn interfaces respectively.
                It should work

                1 Reply Last reply Reply Quote 0
                • A
                  ariban99
                  last edited by

                  hi
                  so i am lost, how do i do all the above? sorry i dont know this stuff very well.
                  any tutorials to follow?

                  1 Reply Last reply Reply Quote 0
                  • N
                    netblues
                    last edited by

                    0_1544569745054_57fb7ca2-e5ed-4ad9-bba1-80d271d305b4-image.png

                    Here is an example.
                    There are two tunnels 192.168.126.0/24 and 192.168.127.0/24 with two interfaces
                    One rule specifies source 192.168.126.0/24 target 192.168.127.0/24 and send packets to 192.168.127.0 assigned gateway.
                    a second rule does the opposite
                    All this under firewall rules openvpn.

                    1 Reply Last reply Reply Quote 0
                    • A
                      ariban99
                      last edited by

                      i will try that, thank you for all your help

                      1 Reply Last reply Reply Quote 0
                      • chpalmerC
                        chpalmer
                        last edited by

                        Tunnel addresses are usually in the same subnet..

                        Triggering snowflakes one by one..
                        Intel(R) Core(TM) i5-4590T CPU @ 2.00GHz on an M400 WG box.

                        1 Reply Last reply Reply Quote 0
                        • A
                          ariban99
                          last edited by

                          so i dont think i am doing it correctly.
                          i assigned OPT1 and OPT2 for the openvpn
                          so OPT1 is for 192.168.2.0
                          and OPT2 is for 192.168.3.0

                          then enabled them.

                          under rules, OPENVPN tab.
                          i create a new rule.
                          interface, WAN
                          IPV4
                          ANY
                          source, i selected OPT1
                          destination OPT2

                          and i did the reverse for the second openvpn but its still not working.
                          what am i doing wrong?

                          1 Reply Last reply Reply Quote 0
                          • chpalmerC
                            chpalmer
                            last edited by

                            Your "Tunnel" networks.. put both sides of the VPN tunnel in the same subnet.

                            tunnel 10.0.3.0/30 When you do this each box will take an address in this subnet.0_1544574635294_tunnel.jpg

                            Triggering snowflakes one by one..
                            Intel(R) Core(TM) i5-4590T CPU @ 2.00GHz on an M400 WG box.

                            chpalmerC 1 Reply Last reply Reply Quote 0
                            • chpalmerC
                              chpalmer @chpalmer
                              last edited by

                              @chpalmer
                              On your second VPN tunnel use a different subnet..

                              Triggering snowflakes one by one..
                              Intel(R) Core(TM) i5-4590T CPU @ 2.00GHz on an M400 WG box.

                              1 Reply Last reply Reply Quote 0
                              • chpalmerC
                                chpalmer
                                last edited by

                                I never assign my own OpenVPN sessions to an interface on the box. So you might be seeing another issue that I wouldn't see but the information above is correct either way. IP Tunnel network on each side should be in the same subnet.

                                Remote network is the network(s) of the box on the other side.

                                Triggering snowflakes one by one..
                                Intel(R) Core(TM) i5-4590T CPU @ 2.00GHz on an M400 WG box.

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

                                  @ariban99 said in connected but cant access vpn lan after upgrade to 2.4.4 p1:

                                  so i dont think i am doing it correctly.
                                  i assigned OPT1 and OPT2 for the openvpn
                                  so OPT1 is for 192.168.2.0
                                  and OPT2 is for 192.168.3.0

                                  You do not number OpenVPN assigned interfaces. You simply assign them then enable them then bounce that OpenVPN instance. You do not specifically number them in the interface configuration. Might be misunderstanding what you're doing but that's what I read.

                                  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)

                                  N 1 Reply Last reply Reply Quote 0
                                  • N
                                    netblues @Derelict
                                    last edited by

                                    Just assign interfaces to openvpn tunnels.
                                    DON'T put ip's there, it will happen automaticaly by openvpn.

                                    chpalmerC 1 Reply Last reply Reply Quote 0
                                    • chpalmerC
                                      chpalmer @netblues
                                      last edited by

                                      @netblues said in connected but cant access vpn lan after upgrade to 2.4.4 p1:

                                      Just assign interfaces to openvpn tunnels.
                                      DON'T put ip's there,

                                      Just like Derelict said..

                                      What does assigning tunnels to interfaces get over just building the tunnel on the router and not assigning them to interfaces? Just curious..

                                      Triggering snowflakes one by one..
                                      Intel(R) Core(TM) i5-4590T CPU @ 2.00GHz on an M400 WG box.

                                      N 1 Reply Last reply Reply Quote 0
                                      • N
                                        netblues @chpalmer
                                        last edited by

                                        @chpalmer said in connected but cant access vpn lan after upgrade to 2.4.4 p1:

                                        Just assign interfaces to openvpn tunnels.
                                        DON'T put ip's there,

                                        It creates the interfaces so you can policy route, add rules, monitor traffic, etc...

                                        1 Reply Last reply Reply Quote 0
                                        • chpalmerC
                                          chpalmer
                                          last edited by

                                          Thanks!

                                          From your list the only thing it seems I don't have is the ability to monitor with the graphs.. you would have to elaborate on the ect..

                                          But just curious..

                                          Triggering snowflakes one by one..
                                          Intel(R) Core(TM) i5-4590T CPU @ 2.00GHz on an M400 WG box.

                                          N 1 Reply Last reply Reply Quote 0
                                          • N
                                            netblues @chpalmer
                                            last edited by

                                            @chpalmer https://www.netgate.com/docs/pfsense/book/openvpn/assigning-openvpn-interfaces.html

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