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

    NEW CARP Setup seems to have a mind of it's own and secret firewall rules - limited/no logs

    HA/CARP/VIPs
    2
    24
    1.8k
    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.
    • H
      Hass
      last edited by

      This is a quick diagram, doesn't show all the access layer etc..

      47381efe-a576-4d79-be02-33da44e84a15-image.png

      1 Reply Last reply Reply Quote 0
      • DerelictD
        Derelict LAYER 8 Netgate
        last edited by

        OK that tells us nothing about how you have it configured.

        Chattanooga, Tennessee, USA
        A comprehensive network diagram is worth 10,000 words and 15 conference calls.
        DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
        Do Not Chat For Help! NO_WAN_EGRESS(TM)

        H 1 Reply Last reply Reply Quote 0
        • H
          Hass @Derelict
          last edited by

          @Derelict I know, notes coming!

          1 Reply Last reply Reply Quote 0
          • DerelictD
            Derelict LAYER 8 Netgate
            last edited by

            does grep 1566102523 /tmp/rules.debug show anything?

            Chattanooga, Tennessee, USA
            A comprehensive network diagram is worth 10,000 words and 15 conference calls.
            DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
            Do Not Chat For Help! NO_WAN_EGRESS(TM)

            1 Reply Last reply Reply Quote 0
            • H
              Hass
              last edited by

              @Derelict nope it returns nothing and when I look in the debug file again I don't see that rule.

              FYI, the other item I'm not sure we changed was to edit the manual outbound NAT rules in the same way we did for the WAN it from the interface to the VIP. I just thought of that, not sure how that relates to these lost rules

              1 Reply Last reply Reply Quote 0
              • DerelictD
                Derelict LAYER 8 Netgate
                last edited by

                No idea what that means. You only need outbound NAT for WANs in general.

                Chattanooga, Tennessee, USA
                A comprehensive network diagram is worth 10,000 words and 15 conference calls.
                DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
                Do Not Chat For Help! NO_WAN_EGRESS(TM)

                1 Reply Last reply Reply Quote 0
                • H
                  Hass
                  last edited by

                  thanks, that answers that then!

                  1 Reply Last reply Reply Quote 0
                  • DerelictD
                    Derelict LAYER 8 Netgate
                    last edited by Derelict

                    Set outbound NAT on WANs to a CARP VIP for sources that need NAT (inside networks, etc. NOT localhost or the WAN subnet or source any)

                    Set DHCP to give a LAN CARP VIP as the default gateway to inside hosts.

                    Set DHCP to give a CARP VIP as the DNS server to inside hosts if you are using pfSense for DNS.

                    Configure the failover peer in the DHCP servers on the Primary to the IP address ON THAT INTERFACE on the secondary.

                    Configure XMLRPC sync on the sync interface on the primary to the secondary - not the other way around.

                    Configure pfsync on the sync interface bidirectionally on both nodes.

                    That's pretty much it.

                    Chattanooga, Tennessee, USA
                    A comprehensive network diagram is worth 10,000 words and 15 conference calls.
                    DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
                    Do Not Chat For Help! NO_WAN_EGRESS(TM)

                    1 Reply Last reply Reply Quote 0
                    • H
                      Hass
                      last edited by

                      Thanks @Derelict I'll step through this all again now and check them off, the only one I know didn't work the last time was DNS (line below). But I'll test that agin on a VLAN now being used. FYI, we're using DNS Resolver (within pfSense)

                      Set DHCP to give a CARP VIP as the DNS server to inside hosts if you are using pfSense for DNS.

                      1 Reply Last reply Reply Quote 0
                      • DerelictD
                        Derelict LAYER 8 Netgate
                        last edited by Derelict

                        It should work for DNS to send them to both nodes' interface addresses but if one is down it will have to time out and might induce client-perceptible delays. If you want multiple DNS servers for your clients my suggestion would be to put them on something off the firewall/HA pair, such as dedicated unbound/BIND servers, domain controllers, etc.

                        Chattanooga, Tennessee, USA
                        A comprehensive network diagram is worth 10,000 words and 15 conference calls.
                        DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
                        Do Not Chat For Help! NO_WAN_EGRESS(TM)

                        1 Reply Last reply Reply Quote 0
                        • H
                          Hass
                          last edited by

                          @Derelict Yes understood and we tried to set it to the CARP vip it just didn't provide an DNS resolution. But testing again now

                          1 Reply Last reply Reply Quote 0
                          • DerelictD
                            Derelict LAYER 8 Netgate
                            last edited by

                            You can always just dig @carp_vip www.google.com from an inside host to see if unbound is listening there. It should be.

                            Chattanooga, Tennessee, USA
                            A comprehensive network diagram is worth 10,000 words and 15 conference calls.
                            DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
                            Do Not Chat For Help! NO_WAN_EGRESS(TM)

                            1 Reply Last reply Reply Quote 0
                            • H
                              Hass
                              last edited by

                              @Derelict it looks like DNS on the .1 (CARP VIP) works on the two OPT networks (GUEST and LAB) but not on the LAN Network. I just get a timed out when I try and lookup against DNS on the LAN CARP VIP

                              1 Reply Last reply Reply Quote 0
                              • DerelictD
                                Derelict LAYER 8 Netgate
                                last edited by Derelict

                                Are you passing DNS traffic to the LAN CARP VIP on that interface?

                                Did you change the default listening interfaces on unbound from All?

                                Is the source address of the query from an address on a pfSense interface or from a network routed from a downstream router on LAN?

                                Anything interesting logged in the DNS Resolver logs?

                                Chattanooga, Tennessee, USA
                                A comprehensive network diagram is worth 10,000 words and 15 conference calls.
                                DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
                                Do Not Chat For Help! NO_WAN_EGRESS(TM)

                                1 Reply Last reply Reply Quote 0
                                • H
                                  Hass
                                  last edited by

                                  Hi Have the interface in DNS Resolver setup with the LAN and LAN CARP VIP highlighted.

                                  If I try and do a packet capture of the firewall on the LAN interface for that LAN CARP VIP, I don't see any traffic for a DNS lookup or even a PING (which works).

                                  FYI< I checked this on both firewalls to be sure.

                                  Hass

                                  1 Reply Last reply Reply Quote 0
                                  • H
                                    Hass
                                    last edited by

                                    I tried a DENY rule to see if I could just get the firewall to say something but no dice

                                    b9828745-7d8b-4341-bbf1-695ea1cf7a51-image.png

                                    1 Reply Last reply Reply Quote 0
                                    • H
                                      Hass
                                      last edited by

                                      !!!!!!!!, it might have been the old Firewall, it had been disabled but when I took a loot at it, it still had a light of lights on the ports... I'm going back through all my testing now.

                                      I just wanted to let you know @Derelict

                                      1 Reply Last reply Reply Quote 0
                                      • H
                                        Hass
                                        last edited by

                                        @Derelict Just wanted to let you know know it's looking allot better now and I think it was just that lingering interface that should have been down that caused the issue (which then caused others).

                                        Thanks for coming back so quick on a Sunday. FYI, I've now hit another Intel 10G known issue which I'll post once I re-read the previous ones

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