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

Open port 1004 on openvpn

Scheduled Pinned Locked Moved OpenVPN
13 Posts 3 Posters 1.2k 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.
  • F
    faxmodem
    last edited by Dec 18, 2017, 3:45 PM

    open vpn client ip :192.168.200.0/24

    1 Reply Last reply Reply Quote 0
    • G
      GoldFish
      last edited by Dec 18, 2017, 3:50 PM

      Can you send a screenshot of telnet.

      Telnet from the open vpn client to 192.168.10.55 1004

      • pfSense Enthusiast *
      1 Reply Last reply Reply Quote 0
      • F
        faxmodem
        last edited by Dec 18, 2017, 3:59 PM

        im use this command : telnet 192.168.10.55 1004  on openvpn client

        On this page, the screen is blinking and has no reaction

        1 Reply Last reply Reply Quote 0
        • G
          GoldFish
          last edited by Dec 18, 2017, 4:03 PM

          Ok. That shows your port is open and visible to the vpn clients.

          If a blank screen appears then the port is open, and the test is successful.
          If you receive a connecting… message or an error message then something is blocking that port.

          But the port is working for you

          • pfSense Enthusiast *
          1 Reply Last reply Reply Quote 0
          • F
            faxmodem
            last edited by Dec 18, 2017, 4:18 PM Dec 18, 2017, 4:12 PM

            but in openvpn user clinet error  my_ip_address_public error
            76.125.x.x 1004 cannot connet

            port 1004 open in web server ip (local : 192.168.10.55)

            1 Reply Last reply Reply Quote 0
            • G
              GoldFish
              last edited by Dec 18, 2017, 4:25 PM

              Thats completely different. You have to do a port forward if you are trying to access it using Wan IP.

              You can do it in Firewall / NAT / Port Forward

              More on port forwarding https://doc.pfsense.org/index.php/How_can_I_forward_ports_with_pfSense

              • pfSense Enthusiast *
              1 Reply Last reply Reply Quote 0
              • F
                faxmodem
                last edited by Dec 18, 2017, 4:48 PM

                like this?

                1 Reply Last reply Reply Quote 0
                • G
                  GoldFish
                  last edited by Dec 18, 2017, 4:54 PM

                  Under Destination Address i would select "Single Host or Alias" instead of "Wan address" and add 192.168.10.55

                  • pfSense Enthusiast *
                  1 Reply Last reply Reply Quote 0
                  • D
                    Derelict LAYER 8 Netgate
                    last edited by Dec 18, 2017, 7:03 PM

                    What? That port forward looks fine.

                    There should be a corresponding firewall rule on WAN passing traffic to 192.168.10.55 port 1004. By default it would have been automatically created.

                    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
                    • G
                      GoldFish
                      last edited by Dec 18, 2017, 7:08 PM

                      He messaged me. He is double natting. Thats another issue. His WAN ip is a private address and not the actual public ip

                      • pfSense Enthusiast *
                      1 Reply Last reply Reply Quote 0
                      • D
                        Derelict LAYER 8 Netgate
                        last edited by Dec 18, 2017, 8:21 PM

                        Does not matter. All that means is he has to forward from upstream too.

                        The traffic will still arrive to WAN address:1004. That is what needs to be forwarded.

                        If the upstream router knows about the 192.168.10.55 address he's doing it wrong.

                        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
                        12 out of 13
                        • First post
                          12/13
                          Last post
                        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
                          This community forum collects and processes your personal information.
                          consent.not_received