You can export only portions of the config.
As for deleting the interface in cli withour making the proper changes in
the config xml is not something i would advise at all. If you are sure you
know how to do it you can edit the running config. Then use cli to remove
the vip. If you want to do it cleanly I would suggest config edit followed
by reboot or config export/import. All this would be workarounds since this
seems to be a bug caused by a edge case. See the doc wiki or forum for
propper xml edit procedures.
18. aug. 2014 20:16 skrev "Adam Williams" <[email protected]> følgende:

> If it's that simple, I can use `viconfig` to delete the `<ipalias>`
> element, then in FreeBSD, simply remove the IP address from the WAN
> interface. I just am not terribly sure of the lifecycle of the config
> file.
>
> On Mon, Aug 18, 2014 at 1:53 PM, Espen Johansen <[email protected]> wrote:
> > Export config. Edit. Then import.
> >
> > 18. aug. 2014 19:21 skrev "Adam Williams" <[email protected]> følgende:
> >>
> >> Hello.
> >>
> >> I am running 2.1-RELEASE (built on Wed Sep 11 18:16:44 EDT 2013),
> >> which I believe includes the fix for the bug documented here
> >> https://redmine.pfsense.org/issues/2406, according to the release
> >> notes at https://redmine.pfsense.org/versions/5.
> >>
> >> In that ticket, it says:
> >>
> >> > You can't remove the last IP alias on the subnet of a CARP IP because
> >> > it'll break CARP, you have to delete the CARP IP first. The only
> exception
> >> > being when the interface IP is on the CARP IP's subnet, which is also
> >> > handled correctly.
> >>
> >> I believe I meet the "only exception" clause, since my WAN interface
> >> is configured for the same subnet of the CARP address.
> >>
> >> I have the following configuration:
> >>
> >> ```
> >>         <interfaces>
> >>                 <wan>
> >>                         <enable/>
> >>                         <if>em5</if>
> >>                         <descr><![CDATA[WAN]]></descr>
> >>                         <blockpriv/>
> >>                         <blockbogons/>
> >>                         <spoofmac/>
> >>                         <ipaddr>2.2.2.1</ipaddr>
> >>                         <subnet>28</subnet>
> >>                         <gateway>WANGW</gateway>
> >>                 </wan>
> >> </interfaces>
> >> <virtualip>
> >>                 <vip>
> >>                         <mode>carp</mode>
> >>                         <interface>wan</interface>
> >>                         <vhid>2</vhid>
> >>                         <advskew>0</advskew>
> >>                         <advbase>1</advbase>
> >>                         <password>bbbbbbbb</password>
> >>                         <descr><![CDATA[CARP]]></descr>
> >>                         <type>single</type>
> >>                         <subnet_bits>28</subnet_bits>
> >>                         <subnet>2.2.2.9</subnet>
> >>                 </vip>
> >>                 <vip>
> >>                         <mode>ipalias</mode>
> >>                         <interface>wan</interface>
> >>                         <descr><![CDATA[Alias]]></descr>
> >>                         <type>single</type>
> >>                         <subnet_bits>28</subnet_bits>
> >>                         <subnet>2.2.2.10</subnet>
> >>                 </vip>
> >> </virtualip>
> >> ```
> >>
> >> However, I cannot delete this IP Alias, being given the message "This
> >> entry cannot be deleted because it is still referenced by a CARP IP
> >> with the description Alias." Of course, there is no CARP address with
> >> that description, so it seems to be referencing the Alias itself!
> >>
> >> It's interesting to note that the `<subnet>` element of the WAN
> >> interface is `28`, where the similarly named element of the VIP
> >> address is `2.2.2.10`, but the `<subnet_bits>` does match the
> >> `<subnet>` element of the interface.
> >>
> >> Does anyone know a workaround so that I can delete this IP Alias?
> >>
> >> Thanks!
> >> _______________________________________________
> >> List mailing list
> >> [email protected]
> >> https://lists.pfsense.org/mailman/listinfo/list
> >
> >
> > _______________________________________________
> > List mailing list
> > [email protected]
> > https://lists.pfsense.org/mailman/listinfo/list
> _______________________________________________
> List mailing list
> [email protected]
> https://lists.pfsense.org/mailman/listinfo/list
_______________________________________________
List mailing list
[email protected]
https://lists.pfsense.org/mailman/listinfo/list

Reply via email to