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

    Help for CARP configuration with a single FO IP

    Scheduled Pinned Locked Moved HA/CARP/VIPs
    15 Posts 2 Posters 2.3k 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.
    • V
      viragomann
      last edited by

      What is the CARP status page showing?
      Status > CARP

      M 1 Reply Last reply Reply Quote 0
      • M
        mourad13 @viragomann
        last edited by

        @viragomann

        Hello,

        Here is a capture of the CARP status
        Primary:
        carp state.PNG
        Backup:
        carp state backup.PNG

        As I said, from a client behind the firewall, when I ping 8.8.8.8, the response comes from 192.168.10.250.
        If I turn off the primary firewall, the response comes from Backup (192.168.10.251).
        Does this sound like a routing problem?
        So far everything is ok.

        On this tutorial (in French), he talks about creating a default gateway.
        Is that related?

        Cordially.

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

          I think, you're are missing the outbound NAT rule. You must set the Outbound NAT to use the CARP IP instead of the interface IP for packets sending out to WAN.

          M 1 Reply Last reply Reply Quote 0
          • M
            mourad13 @viragomann
            last edited by mourad13

            @viragomann
            Here is the NAT rule for the concerned VLAN.
            NAT detail.PNG

            I have already put the VIP address instead of the interface address.

            1 Reply Last reply Reply Quote 0
            • M
              mourad13
              last edited by mourad13

              Here is some additional info. I tested the progress of a request (from the web server to google). the results are as follows (The previous captures already show the pind from the server to the OPT10 VIP):

              OPT10 VIP to OPT10 interface = OK:
              OPT10 VIP vers OPT10 interface.PNG

              OPT10 interface to WAN interface = OK:
              OPT10 interface vers WAN interface.PNG

              WAN interface to WAN VIP = OK:
              WAN interface vers WAN VIP.PNG

              WAN VIP to 8.8.8.8 = KO:
              WAN VIP vers goole.PNG

              OPT10 VIP to WAN VIP = OK:
              OPT10 VIP vers WAN VIP.PNG

              OPT10 to 8.8.8.8 = KO:
              OPT10 interface vers google.PNG

              I have a default route (via shellcmd):
              shellcmd.PNG

              1 Reply Last reply Reply Quote 0
              • M
                mourad13
                last edited by

                One more info, when I do a traceroute on my production (only 1 Pfsense), the 1st line corresponds to the gateway of my Proxmox host (In reality, the exact gateway, the one I added on the way via shellcmd , finished in .254. I don't know why the tracert returns .252, but it works) :
                tracert prod.PNG

                On the other hand, from the server on which I am performing my tests, it does not work:
                tracert test.PNG

                The problem seems to come from there.

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

                  That now seems to be a bit more complex with your default gateway on Proxmox. Why do you need this?

                  Can you provide a drawing of your (virtual) network?

                  And why do you set the routes via shellcmd? I can't see anything which can't be done natively in pfSense?

                  M 1 Reply Last reply Reply Quote 0
                  • M
                    mourad13 @viragomann
                    last edited by

                    @viragomann

                    Hello @viragomann

                    The Proxmox gateway is, to my knowledge, necessary, because it is a failover IP used by the Pfsense WAN. I added his MAC address in his Proxmox configuration.
                    Here is a network diagram:
                    network.png

                    Regarding shellcmd, I followed a tutorial. this is to apply the rules automatically each time the VM is restarted.

                    I continue to do checks, I realized, the shellcmd command does not work since the implementation of the HA.
                    As we see in the capture below, the road is missing add.

                    Route on the production:
                    route prod.PNG

                    Route on the Test:
                    route test.PNG

                    While waiting for a response, I will try to add the missing routes.

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

                      @mourad13 said in Help for CARP configuration with a single FO IP:

                      The Proxmox gateway is, to my knowledge, necessary, because it is a failover IP used by the Pfsense WAN.

                      So this seems to be your upstream gateway.

                      Does Proxmox also have an IP in your WAN subnet?

                      Do a packet capture on the WAN interface with ICMP filter, while you try a ping to verify the outbound NAT is working.

                      1 Reply Last reply Reply Quote 0
                      • M
                        mourad13
                        last edited by mourad13

                        @viragomann
                        I had hidden the IPs, but it doesn't matter. This is a server that will soon be terminated and which is only used for these tests currently.

                        The IP of the Proxmox server is 37.59.49.15
                        The Proxmox gateway is 37.59.49.254

                        The Failover IP (WAN VIP) is 146.59.130.46/32

                        I tried to capture the packets, but I have no results (except the 2 OVH IPs for monitoring).
                        I did a ping from Pfsense and from a client behind OPT10.
                        I only have results when the capture is on OPT10.

                        WAN :
                        capture conf.PNG
                        Capture.PNG

                        OPT10 :
                        Capture OPT10.PNG

                        However, when I ping the VIP WAN IP from the client, the ping is OK, but no capture.

                        I managed to reproduce the same routes as on my production, but only in cmd. I can't get from the interface (because of the mac address in the gateway and the / 32).

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

                          @mourad13 said in Help for CARP configuration with a single FO IP:

                          The Proxmox gateway is 37.59.49.254
                          The Failover IP (WAN VIP) is 146.59.130.46/32
                          WAN => 192.168.100.1

                          The gateway you're trying to access does not reside within any of the pfSense subnets.
                          So I assume now, the route commands in shellcmd should provide a kind of PPP. Otherwise the gateway can't be reachable from pfSense.
                          However, I'm not familiar with such configuration and cannot say if you have done it correctly. Also I'm not sure if that can work from the view of the gateway. I think the gateway has to support PPP as well.

                          M 1 Reply Last reply Reply Quote 0
                          • M
                            mourad13 @viragomann
                            last edited by

                            @viragomann

                            Thank you anyway for your help. This allowed me to identify the problem and better diagnose a routing problem.

                            For my part, I carried out some test and I saw the change.
                            In the routing table, without a gateway, the "use" column remains at 0.

                            When I put the Proxmox gateway, some traffic seems to be detecting.
                            I think it's a routing or NAT problem.

                            Gateway :
                            gw.PNG

                            Route :
                            route ok.PNG

                            According to this tutorial (in French), it should however work.
                            The only difference is, potentially, the / 32 mask.
                            https://voiprovider.wordpress.com/2017/03/26/la-ha-avec-pfsense-et-1-seule-ip-wan/

                            I will probably create another post in the "routing" category with a link to this post.

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