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

    Remote OpenVPN client traffic being blocked because of Public IP address

    Scheduled Pinned Locked Moved OpenVPN
    5 Posts 4 Posters 1.4k 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.
    • R
      ross682003
      last edited by

      I am running PfSense 2.2.4.  I have an Asterisk PBX behind the firewall.  I set up OpenVPN with SSL/TLS + User auth.  When I have my remote users try to connect their SIP client software to the PBX, it will ring and connect but no audio.  I have discovered that it is trying to connect the RTP connections by using the remote user's public IP address NOT the tunnel network.  This will not work due to the fact they are access the PBX with different public ip's.  The OpenVPN server is using the wan interface.  Any assistance would be appreciated.

      1 Reply Last reply Reply Quote 0
      • E
        ega
        last edited by

        Active the option "Force all client generated traffic through the tunnel." on OpenVPN Server.

        Si compartes dinero queda la mitad, si compartes conocimiento queda el doble.-

        1 Reply Last reply Reply Quote 0
        • R
          ross682003
          last edited by

          ega

          Thanks for the information but that did not work.  When look in the firewall system logs it shows it blocking packets from the public IP address of the remote user running the openvpn client.

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

            What are your OpenVPN firewall rules?

            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)

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

              Why would the traffic for you public IP go thru the tunnel, did you hand out routes to the clients that the public IP is down the tunnel?  When your call is ssetup, the client should be told what the private IP is so it will go down the tunnel just like the call setup.

              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.