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

    Pfsense Azure - Internet by WAN and not by Azure

    Scheduled Pinned Locked Moved Firewalling
    5 Posts 4 Posters 1.0k Views 4 Watching
    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 Offline
      Brownie
      last edited by

      I installed Pfsense on Azure from a VHD disk that i have uploaded.

      There is 1 network : 172.0.0.0/16
      There are 2 subnets : 172.0.0.0/24 (WAN Interface) and 172.0.1.0/24 (LAN Interfaces).
      On my Pfsense, i have 2 network interfaces : 172.0.0.5 and 172.0.1.5

      I have some Windows servers behind my Pfsense. I want that theeses servers go to internet passing by Pfsense.

      By default, Azure have a route to go directly on Internet. To change it, i created a "Route Table" on Azure.
      I configured this route :

      Adress prefix : 0.0.0.0/0
      Next hop adress : 172.0.1.5

      With an ICMP rule, i can ping Google from WAN but not from LAN.

      Please, is anyone have an idea to help me ?

      A 1 Reply Last reply Reply Quote 0
      • C Offline
        ChrisT
        last edited by

        Similar issue here. Have you managed to make it work?

        1 Reply Last reply Reply Quote 0
        • A Offline
          aomiglionni @Brownie
          last edited by

          @brownie I'm having the same problem on Azure with a pfsense virtual appliance, but in my case I have more vnets connected by peering that I can't connect. How did you solve the problem?

          B 1 Reply Last reply Reply Quote 0
          • B Offline
            Brownie @aomiglionni
            last edited by

            @aomiglionni
            Hi,
            I finally didn't use pfsense on Azure because I didn't need it.
            But you certainly have to manipulate the NSG rules. There are some rules created by default by Azure.
            I think you have to create rules by disallowing access from/to the internet. You also need to put a lower priority than the default rules.

            A 1 Reply Last reply Reply Quote 0
            • A Offline
              alejjime @Brownie
              last edited by

              Hi @brownie and @aomiglionni, I have the same scenario and I am having the same issue. I have created rules in the nsg allowing all the ports, because, as @Brownie says, the default rules stop all the ports. But the problem of connection persist.

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