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

    Incoming port 80, 25 & 443 sent across OpenVPN to alternate location...

    Scheduled Pinned Locked Moved OpenVPN
    2 Posts 2 Posters 362 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.
    • D
      dovad
      last edited by

      I would like to setup a server on my home network which is a typical residential connection where ports 80 and 25 are blocked. I have pfSense on my home network as well as my office. My office has a business Internet service where all ports are available. At the office we do not use nor need ports 80, 25 or 443, we don’t host any servers. I have a domain which I can have the DNS point to my office static IP address but would like the incoming activity on the above ports sent to my home server across OpenVPN.

      If someone can give me some pointers on how to set this up I’d be very grateful.

      Thanks…
      Dave

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

        The images are gone for the time being at least but see the post regarding ssh here:

        https://forum.netgate.com/topic/74534/a-definitive-example-driven-openvpn-reference-thread/5

        The key is you need an assigned interface on the side with the server that is receiving the connections and the rules that pass the traffic MUST NOT match the rules on the OpenVPN tab. They must match the rules on the assigned interface tab or you will not get reply-to so you won't have good two-way traffic.

        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
        • First post
          Last post
        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.