Navigation

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

    Port forwarding on IP addresses other than WAN Address

    Firewalling
    3
    4
    261
    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.
    • B
      benjoi87 last edited by

      Hi All,

      So I have a an issue that is confusing me a little.
      I have a multiple External IP addresses that I've added to the router as VIPs after reading that was the way to do it in pfsense. I'm slightly confused when port forwarding though.
      I add a NAT>Portforward with the following settings:
      Interface: WAN
      Protocol: TCP
      Destination: (select VIP for the external IP I want to port forward)
      Destination Port Range: From: https To: HTTPS
      Redirected Target IP: 192.168.101.154
      Redirected Port: HTTPS
      NAT Reflection: Use System Defaults

      When I test the port externally it's saying the port is closed and nothing appears to get through. I'm sure I'm doing something wrong but can't figure out what.
      Any help would be awesome!

      Thanks,
      Ben

      1 Reply Last reply Reply Quote 0
      • Grimson
        Grimson Banned last edited by

        https://doc.pfsense.org/index.php/Port_Forward_Troubleshooting

        1 Reply Last reply Reply Quote 0
        • B
          benjoi87 last edited by

          @Grimson:

          https://doc.pfsense.org/index.php/Port_Forward_Troubleshooting

          Thanks for the reply. Appreciate it.
          I've already been through that troubleshooting guide and as far as I can see everything should work. I'll remove the rules I've created and go again from the start I think to see if I've made any silly mistake I haven't noticed.

          Ben

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

            Well one of the steps in the troubleshooting is to sniff to make sure the traffic your wanting to forward is actually getting to your wan to be forwarded.  If you see the traffic get there, then validate it is being sent out the lan side interface to your destination IP.. If so then pfsense is doing what you told it to do, if the client doesn't answer maybe there is a firewall on that host, maybe that host uses a different gateway then pfsense.

            Quite often that traffic never even gets to pfsense for it to forward, or user puts in wrong dest IP, or maybe even that service is not even listening on that port your forwarding to, etc.

            Troubleshooting a port forward really should take no more than a couple of minutes to validate traffic via a sniff.

            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
            2440 2.4.5p1 | 2x 3100 2.4.4p3 | 2x 3100 22.01 | 4860 22.05

            1 Reply Last reply Reply Quote 0
            • First post
              Last post