Navigation

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

    Open port 1004 on openvpn

    OpenVPN
    3
    13
    429
    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.
    • faxmodem
      faxmodem last edited by

      i'm create openpvn

      Users should be able to see the port number 1004 On the internal network address 192.168.10.55 and
      It should also be visible through the network's public address
      in openvpn rule open any port bunt openvpn userse can not see port 1004 on local network ip 192.168.10.55



      1 Reply Last reply Reply Quote 0
      • G
        GoldFish last edited by

        Whats the subnet for OpenVPN clients. Can they ping 192.168.10.55 once connected to VPN?

        • pfSense Enthusiast *
        1 Reply Last reply Reply Quote 0
        • faxmodem
          faxmodem last edited by

          open vpn client ip :192.168.200.0/24

          1 Reply Last reply Reply Quote 0
          • G
            GoldFish last edited by

            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
            • faxmodem
              faxmodem last edited by

              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

                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
                • faxmodem
                  faxmodem last edited by

                  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

                    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
                    • faxmodem
                      faxmodem last edited by

                      like this?

                      1 Reply Last reply Reply Quote 0
                      • G
                        GoldFish last edited by

                        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
                        • Derelict
                          Derelict LAYER 8 Netgate last edited by

                          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
                          The pfSense Book is free of charge!
                          DO NOT set a source 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

                            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
                            • Derelict
                              Derelict LAYER 8 Netgate last edited by

                              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
                              The pfSense Book is free of charge!
                              DO NOT set a source 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
                              • First post
                                Last post