Navigation

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

    VM PfSense on PROXMOX

    Firewalling
    2
    2
    289
    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
      BeckerIbero last edited by

      Hi I have PfSense installed in a virtual machine inside a dedicated server in OVHCloud with PROXMOX.

      This server already offers me a WAN interface called "enp1s0f0" and I have created a LAN called "enp1s0f1".

      alt text

      The virtual machine running PfSense is configured as follows

      alt text

      The interface (net0) has a MAC that comes with a Failover IP which is the one I have assigned as WAN in PfSense.

      And the interface (net1) is the one I use as LAN.

      (net2) is a MAC of another Failover IP that I plan to NAT from PfSense and connect to the Firewall from a LAN IP address.

      This is the configuration I have made in OPT1 to do NAT to the Failover IP that has the MAC: 02:00:00:56:84:e1

      OPT1:

      alt text

      Gateway:

      alt text

      NAT Rules:

      alt text

      LAN configuration on the Windows network adapter:

      alt text

      Everything seems to be working fine, however my problem is when surfing the internet, instead of going out to the internet with 51.79.33.215, it comes out with the WAN IP of PfSense (142.44.180.21).

      alt text

      I would like to somehow make each IP go out with the Failover IP that I have configured in PfSense and not with the WAN IP of the same one.

      V 1 Reply Last reply Reply Quote 0
      • V
        viragomann @BeckerIbero last edited by

        @beckeribero
        In the OPT1 interface settings you might have to change the mask to /24 so that pfSense can communicate with the failover gateway.

        Outbound traffic is directed out according to the routing table or even the default gateway setting in System > Routing > Gateways.

        You can create one or multiple gateway group for automatic failover and state this as default gateway or in policy routing rules.
        If you want to direct out the upstream traffic of certain local devices to a certain non-default gateway, you have to do this with policy routing rules:
        In the rule, which allow the upstream traffic, open the advanced settings and select the desired gateway. But ensure that the rule does not match to internal destinations. You can add an additional rule for internal access like DNS without the gateway option and put it above of the policy routing rule.

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