IP alias input validation problem
When you have an interface with IP "none" configured, and have an IP alias on that interface, after adding the IP alias you can no longer edit that IP alias. It triggers input validation "The $interface IP address may not be used in a virtual entry."
<opt2> <descr>OPT2</descr> <if>em3</if> <enable/> <alias-address/> <alias-subnet>32</alias-subnet> <spoofmac/> </opt2>
<vip> <mode>ipalias</mode> <interface>opt2</interface> <descr/> <type>single</type> <subnet_bits>24</subnet_bits> <subnet>192.168.4.5</subnet> </vip>
It's initially added fine, but if you go in and edit it, you cannot save it.
#3 Updated by Ermal Luçi about 9 years ago
I am not sure if there is a solution to this.
I investigated on providing a fix for this but otherwise it will break cases when an openvpn/ppp/gre/gif type interface is assigned.
Not sure if this should be allowed to have an alias for interfaces that do not have an ip address configured at all, since it does not make even sense to have an alias in an interface that has not an ip?!
This alias will be treated as the interface ip. I will look if this can be handled directly in the pfSense php module though i think not.
#4 Updated by Chris Buechler about 9 years ago
It probably really doesn't make sense to add a VIP IP alias on an interface configured without an IP. So the solution can be as simple as not allowing an alias VIP if the interface IP is set to "none". No sense in putting a lot of time into such an unusual situation that people aren't likely to hit anyway.