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

    [Solved] Forward to different WAN address

    Firewalling
    3
    4
    2.1k
    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.
    • V
      veix
      last edited by

      Hello,

      I have been trying various thing with pfsense for 2 hours now and cannot find solution. Probably it is too easy for you, but I have too limited knowledge about firewalls.

      Is there anybody who knows a solution for the next situation:
      I need that when LAN clients try to access address https://172.16.1.5:5555 they will be forwarded to address https://some.site.com:5555

      Setup
      LAN network: 192.168.1.0 mask:255.255.255.0

      Is solution proxy or DNS or routing or Outbount NAT or some firewall rule?

      veix

      1 Reply Last reply Reply Quote 0
      • C
        clarknova
        last edited by

        How about a regular NAT:Port Forward rule on the LAN interface with 172.16.1.5:5555 as the destination and 1.1.1.1:5555 as the redirect target IP, where 1.1.1.1 is the IP address of some.site.com?

        I've never tried this but I think inbound NAT will work in whatever direction you want, no?

        db

        1 Reply Last reply Reply Quote 0
        • C
          cmb
          last edited by

          @clarknova:

          How about a regular NAT:Port Forward rule on the LAN interface with 172.16.1.5:5555 as the destination and 1.1.1.1:5555 as the redirect target IP, where 1.1.1.1 is the IP address of some.site.com?

          I've never tried this but I think inbound NAT will work in whatever direction you want, no?

          Yeah that would work.

          1 Reply Last reply Reply Quote 0
          • V
            veix
            last edited by

            Thx

            Since it was timecritical, we made changes to a client application and did not have add firewall rules.

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