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

    PORT FORWARD NOT WORKING IN AZURE CLOUD SINGLE NIC PFSENSE FIREWEALL

    Scheduled Pinned Locked Moved NAT
    3 Posts 2 Posters 290 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.
    • S
      sandeepvkm
      last edited by

      I HAVE CONFIG AZURE CLOUD NETGATE PFSENSE FIREWALL (SINGLE NIC). BUT NOT ABLE TO CONFIG PORT FORWARD.
      PLEASE LET ME KNOW HOW TO CONFIG PORT FORWARD IN AZURE CLOUD PFSENSE.
      NEED TO CONFIG ANY OUTBOUND NAT POLICY?

      MY PFSENSE CONFIG DETAILS AND SCREENSHOTS ARE FIND BELOW.

      FIREWALL IP(SINGLE NIC)- 172.18.0.254
      VM IP(PORT FORWARD TO THIS VM)- 172.18.0.4
      PORT RDP-3389
      PORT FORWARD CONFIG 2.JPG PORT FORWARD CONFIG 1.JPG FIREWALL RULES.JPG AZURE PFSENSE NSG.JPG

      1 Reply Last reply Reply Quote 0
      • GertjanG
        Gertjan
        last edited by

        Hi,

        Added to your NAT issue : you have also a KEYBORD ISSUE. Repair that first.

        Your other NAT rules, port 22,80 and 443, work well ?
        If so, next question :

        53f03d5a-1314-4d26-91a3-c2d35f24e6a2-image.png

        ?? ( !! )
        The upstream admin might have out-smarted you.
        Change the "3389" port on your windows server.
        And adapt your NAT rule in consequence.

        Btw : the upstream admin is the guy how build this interface :

        daeb2fad-786e-40c0-8c43-e6f5d66ebd00-image.png

        No "help me" PM's please. Use the forum, the community will thank you.
        Edit : and where are the logs ??

        1 Reply Last reply Reply Quote 0
        • S
          sandeepvkm
          last edited by

          @Gertjan said in PORT FORWARD NOT WORKING IN AZURE CLOUD SINGLE NIC PFSENSE FIREWEALL:

          port 22,80 and 443

          port 22,80 and 443 not working, bcz I'm Only forwarded port 3389 for testing.

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