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

    CARP stuck in "init" and kernel: ifa_add_loopback_route: insertion failed

    Scheduled Pinned Locked Moved HA/CARP/VIPs
    11 Posts 4 Posters 6.8k 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.
    • R
      rkrenzis
      last edited by

      Having problem after upgrading to pfSense 2.0.1 using the "auto-update" feature built into the UI.  Status shows carp interfaces in "INIT" -and- I'm not using hyper-v.

      Kernel error messages:

      Dec 30 20:29:58 kernel: carp0: changing name to 'vip1'
      Dec 30 20:29:58 kernel: ifa_add_loopback_route: insertion failed
      Dec 30 20:29:59 kernel: carp1: changing name to 'vip3'
      Dec 30 20:29:59 kernel: ifa_add_loopback_route: insertion failed
      Dec 30 20:30:00 kernel: carp2: changing name to 'vip4'
      Dec 30 20:30:00 kernel: ifa_add_loopback_route: insertion failed
      Dec 30 20:30:01 kernel: carp3: changing name to 'vip5'
      Dec 30 20:30:01 kernel: ifa_add_loopback_route: insertion failed
      Dec 30 20:30:02 kernel: carp4: changing name to 'vip2'
      Dec 30 20:30:02 kernel: ifa_add_loopback_route: insertion failed
      Dec 30 20:30:03 kernel: carp5: changing name to 'vip6'
      Dec 30 20:30:03 kernel: ifa_add_loopback_route: insertion failed
      Dec 30 20:30:04 kernel: carp6: changing name to 'vip7'
      Dec 30 20:30:04 kernel: ifa_add_loopback_route: insertion failed
      Dec 30 20:30:05 kernel: carp7: changing name to 'vip8'
      Dec 30 20:30:05 kernel: ifa_add_loopback_route: insertion failed
      Dec 30 20:30:06 kernel: carp8: changing name to 'vip9'
      Dec 30 20:30:06 kernel: ifa_add_loopback_route: insertion failed
      Dec 30 20:30:07 kernel: carp9: changing name to 'vip10'
      Dec 30 20:30:07 kernel: ifa_add_loopback_route: insertion failed
      Dec 30 20:30:08 kernel: carp10: changing name to 'vip11'
      Dec 30 20:30:08 kernel: ifa_add_loopback_route: insertion failed
      Dec 30 20:30:09 kernel: carp11: changing name to 'vip12'
      Dec 30 20:30:09 kernel: ifa_add_loopback_route: insertion failed
      Dec 30 20:30:10 kernel: carp12: changing name to 'vip13'
      Dec 30 20:30:10 kernel: ifa_add_loopback_route: insertion failed

      Please advise if any configuration files need to be posted to assist in troubleshooting.

      1 Reply Last reply Reply Quote 0
      • C
        cmb
        last edited by

        You have a different problem, please don't hijack threads.

        Not enough info here to provide any suggestions. Getting stuck in INIT generally means the interface the CARP IP resides on doesn't exist or has some other problem.

        1 Reply Last reply Reply Quote 0
        • R
          rkrenzis
          last edited by

          Pardon me.  The error message was the same but I missed and I thought it would be helpful in troubleshooting.  Here is more information:

          $ /sbin/sysctl -a | grep -i carp
          net.inet.ip.same_prefix_carp_only: 0
          net.inet.carp.allow: 1
          net.inet.carp.preempt: 0
          net.inet.carp.log: 1
          net.inet.carp.arpbalance: 0
          net.inet.carp.suppress_preempt: 1
          net.link.ether.inet.carp_mac: 0

          An upgrade was done from pfSense 1.2.3 to pfSense 2.0.1.
          Same configuration was working in pfSense 1.2.3.

          Again, the errors from the system log:

          Dec 30 21:47:44 kernel: carp1: changing name to 'vip2'
          Dec 30 21:47:44 kernel: ifa_add_loopback_route: insertion failed
          Dec 30 21:47:44 kernel: carp2: changing name to 'vip3'
          Dec 30 21:47:44 kernel: de2: promiscuous mode enabled
          Dec 30 21:47:44 kernel: ifa_add_loopback_route: insertion failed
          Dec 30 21:47:44 kernel: carp3: changing name to 'vip4'
          Dec 30 21:47:44 kernel: ifa_add_loopback_route: insertion failed
          Dec 30 21:47:44 kernel: carp4: changing name to 'vip5'
          Dec 30 21:47:44 kernel: de1: promiscuous mode enabled
          Dec 30 21:47:44 kernel: ifa_add_loopback_route: insertion failed
          Dec 30 21:47:44 kernel: carp5: changing name to 'vip6'
          Dec 30 21:47:44 kernel: ifa_add_loopback_route: insertion failed
          Dec 30 21:47:44 kernel: carp6: changing name to 'vip7'
          Dec 30 21:47:44 kernel: ifa_add_loopback_route: insertion failed
          Dec 30 21:47:44 kernel: carp7: changing name to 'vip8'
          Dec 30 21:47:44 kernel: ifa_add_loopback_route: insertion failed
          Dec 30 21:47:44 kernel: carp8: changing name to 'vip9'
          Dec 30 21:47:44 kernel: ifa_add_loopback_route: insertion failed
          Dec 30 21:47:44 kernel: carp9: changing name to 'vip10'
          Dec 30 21:47:44 kernel: ifa_add_loopback_route: insertion failed
          Dec 30 21:47:44 kernel: carp10: changing name to 'vip11'
          Dec 30 21:47:44 kernel: ifa_add_loopback_route: insertion failed
          Dec 30 21:47:44 check_reload_status: Reloading filter
          Dec 30 21:47:44 kernel: carp11: changing name to 'vip12'
          Dec 30 21:47:44 kernel: ifa_add_loopback_route: insertion failed
          Dec 30 21:47:44 kernel: carp12: changing name to 'vip13'
          Dec 30 21:47:44 kernel: ifa_add_loopback_route: insertion failed

          Made sure I read the Upgrading to 2.0 guide and ensured that I did not have any special characters.

          1 Reply Last reply Reply Quote 0
          • C
            cmb
            last edited by

            Double check which interface your CARP IPs are configured under. Should log a different error if it's wrong, but double check (1.2.3 was less strict on 100% proper input validation there). Also make sure the mask on the CARP IPs matches the mask on the interface IP within that same subnet (i.e. if your WAN is a /29, make sure your WAN CARP IPs are on WAN, and /29 too).

            If nothing is obviously wrong there, feel free to email me a backup of your config (cmb at pfsense dot org), I've yet to hear anything other than having the wrong interface selected that'll break CARP IPs on an upgrade.

            1 Reply Last reply Reply Quote 0
            • R
              rkrenzis
              last edited by

              Alright, so I can't figure out anything that would stick out.  (head-hit-keyboard).  The subnet is a /28 and /24 respectively for the internal networks, verified the network interface as well.  It's a small network but pfSense 1.2.3 was working great up until the upgrade.  I've sent the configuration file to your email.  If you can't figure it out, no problems – I have the media for pfSense and can re-install with the backup configuration file I made before upgrading.

              1 Reply Last reply Reply Quote 0
              • C
                cmb
                last edited by

                Huh, yeah your config is indeed perfectly fine. And works perfectly on my system, I just changed the password and NICs in the config you sent me and restored it, and get the attached. That leads me to believe it's a NIC driver regression on dc(4), do you have different NICs you could try to confirm or deny that? Those aren't the best hardware in the world anyway, though I know they're decently widely used. That should be the only difference between my system and yours that could impact that.

                status-carp.png
                status-carp.png_thumb

                1 Reply Last reply Reply Quote 0
                • R
                  rkrenzis
                  last edited by

                  The network card in the system is a DEC 21040 quad-ethernet card using the "de" driver.  There is a on board nic but that is not in use.  I'll go an swap out the network card and see if it works.  I'll keep you posted.  Thanks for your help!

                  1 Reply Last reply Reply Quote 0
                  • R
                    rkrenzis
                    last edited by

                    I'm not sure if I should mark the post "fixed" but the old QFE DEC 21040 (de) network card was removed and replaced with 4 intel pro/100 (fxp) cards and the system comes up and running.

                    Thanks for the help.

                    1 Reply Last reply Reply Quote 0
                    • C
                      ChrisH1
                      last edited by

                      Ah-ha! That's the same NIC Hyper-V emulates. So the problem seems to be the "de"-driver rather than Hyper-V itself.

                      Could you re-merge the threads, since we both have the same problem after all?

                      1 Reply Last reply Reply Quote 0
                      • R
                        rkrenzis
                        last edited by

                        I can't re-merge the thread because the moderator separated it.  Same issue still exists with the de driver.

                        1 Reply Last reply Reply Quote 0
                        • I
                          iskull
                          last edited by

                          @rkrenzis:

                          I can't re-merge the thread because the moderator separated it.  Same issue still exists with the de driver.

                          Any solution for "kernel: ifa_add_loopback_route: insertion failed" ?

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