Map interfaces based on mac and give them a name. Then adress the
interfaces based on that name. When it comes to reorganization of
interfaces the answer is; don't do it. Let the user remap interfaces
manually only. If the user wants to drop their DMZ to get wan back online
then it should be a manual process.
In order to accomplish this you need a interface database and a simple
interface setup process with a foreach loop. This code was done in 2007 but
it was never comitted.
Ifconfig allows naming of interfaces. So once they are named and mac->name
binding is done, then the binding is remebered "forever" in a config file.
If a new interface is added and not found in the mac->name "DB" it is just
placed in a unassigned state untill the user assigns it manually.
On Fri, Oct 14, 2016, 18:00 Vick Khera <vi...@khera.org> wrote:
> On Thu, Oct 13, 2016 at 6:25 PM, Walter Parker <walt...@gmail.com> wrote:
> > Problem is that all of the current OS do this sort of renumbering (I'd
> > to check, but I think it could be a hardware/driver issue). IIRC Linux
> > systems have had this sort of problem in even greater measure than the
> > BSDs. The plug and play nature of USB has caused issues for most systems
> Current versions of CentOS/RedHat hard-wire ethernet names. You have
> to go dig in and find some file that has the mappings and delete them
> if you do something like replace a motherboard with embedded NICs,
> otherwise it makes all new ethernet device names for you. The mapping
> is base on MAC address.
> pfSense mailing list
> Support the project with Gold! https://pfsense.org/gold
pfSense mailing list
Support the project with Gold! https://pfsense.org/gold