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

[Fixed] Deleting CARP Virtual IPs "still referenced by at least one Gateway."?

HA/CARP/VIPs
2
4
6.6k
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.
  • C
    cmcdonald Netgate Developer
    last edited by Jul 6, 2013, 9:21 PM Jul 5, 2013, 4:42 AM

    It's late at night and I'm probably over looking something dumb…

    I'm working on doing some reconfiguration of my setup and want to delete a CARP Virtual IP. This is a WAN IP that is within my /29 block from my ISP. My NAT configuration is been set back to translate to the WAN address (instead of the CARP VIP).

    I know I've delete CARP VIPs before... But for some reason I'm getting this message:

    "This entry cannot be deleted because it is still referenced by at least one Gateway."

    Edit: Okay, it appears this functionality was added here:

    https://github.com/pfsense/pfsense/commit/55705b333518144ccea42219c8459b5d0b1d6ecc
    http://redmine.pfsense.org/issues/2962

    This is kind of annoying... I can't just delete the gateway and kill my WAN connection to my boxes... This explains why I could do this on 2.0.3 before i upgraded to 2.1 within the last month or so. The new code definitely needs some modification. I should be able to delete a VIP that isn't used by anything that also happens to sit inside the subnet of my WAN gateway.

    Need help fast? https://www.netgate.com/support

    1 Reply Last reply Reply Quote 0
    • C
      cmcdonald Netgate Developer
      last edited by Jul 6, 2013, 9:21 PM

      Fixed: http://redmine.pfsense.org/issues/3075

      Thanks!

      Need help fast? https://www.netgate.com/support

      1 Reply Last reply Reply Quote 0
      • M
        mrzaz
        last edited by Jul 10, 2013, 6:27 PM

        @vbman213:

        Fixed: http://redmine.pfsense.org/issues/3075

        Thanks!

        I have just updated to the latest build (2.1-RC0 (i386) built on Tue Jul 9 23:03:10 EDT 2013" but still see
        this problem when trying to remove "IP Alias" entries.

        I get "This entry cannot be deleted because it is still referenced by at least one Gateway." when trying
        to remove one IP Alias.   (I only have one primary IP defined in the WAN-interface .51 at end
        and one VirtualIP "IP Alias"with .53 at the end. Is in same subnet as primary IP.

        The "IP Alias" was created in an earlier build from June.

        I was only doing some tests for a colleague and need to undefine the IP Alias as this IP
        is normally used in another router and is temporary disconnected so I could do the test.
        As long as this IP is now tied to pfSense it will answer ARPs and I will get an IP collision.

        Dan Lundqvist
        Stockholm, Sweden

        1 Reply Last reply Reply Quote 0
        • C
          cmcdonald Netgate Developer
          last edited by Jul 11, 2013, 5:00 AM

          @mrzaz:

          @vbman213:

          Fixed: http://redmine.pfsense.org/issues/3075

          Thanks!

          I have just updated to the latest build (2.1-RC0 (i386) built on Tue Jul 9 23:03:10 EDT 2013" but still see
          this problem when trying to remove "IP Alias" entries.

          I get "This entry cannot be deleted because it is still referenced by at least one Gateway." when trying
          to remove one IP Alias.   (I only have one primary IP defined in the WAN-interface .51 at end
          and one VirtualIP "IP Alias"with .53 at the end. Is in same subnet as primary IP.

          The "IP Alias" was created in an earlier build from June.

          I was only doing some tests for a colleague and need to undefine the IP Alias as this IP
          is normally used in another router and is temporary disconnected so I could do the test.
          As long as this IP is now tied to pfSense it will answer ARPs and I will get an IP collision.

          Dan Lundqvist
          Stockholm, Sweden

          I would recommend posting on the issue page @ http://redmine.pfsense.org/issues/3075

          Need help fast? https://www.netgate.com/support

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