pfSense

I tried exactly this on a 2.3.3 VM and it works fine - I made em1_vlan42 and it got assigned to LAN and came back after reboot.
I wonder what is special about "igb" or the SG-2220 or ???

I can confirm this using an RCC-VE 2440 and both netgate factory and CE 2.3.3 images.

I believe this is due to running option 1 (and probably option 2) from the console does not remove /conf/trigger_initial_wizard which must cause some default interface assignment to occur on restart.

Workaround: Assigning VLANs followed by rm /conf/trigger_initial_wizard followed by a reboot left the VLANs (and, presumably, any custom interface assignments) intact.

This seems familiar and smells of regression but might not have ever been fixed from about a year ago.

I could reproduce after doing a "reset to factory defaults" in the VM
PR https://github.com/pfsense/pfsense/pull/3626 fixes it for me.

Note: the workaround here (and often the "natural" workflow) is to use the console menu to set up the VLAN/s then access the webGUI (presumably over the VLAN just created, through a VLAN switch that is connected to the pfSense LAN...) and be presented with the initial setup wizard. You can go through the wizard or bypass it in the webGUI, either way the system knows the initial setup has been done, and the next bot is fine.

The problem is only evident if you use the console menu to set up the VLAN/s then reboot before accessing the webGUI.

Right.

This is probably not the place for this discussion but if a manual assignment is done in the web menu/CLI prior to entering the webgui and the setup wizard, all the console menu function has to do is unlink /conf/trigger_initial_wizard when it saves its work and everyone is happy and experiences the expected result.

I often do an initial interface configuration from the CLI. This only appears immediately after an install or factory reset.

Should have looked at your patch first. That is why I say IANAProgrammer.

The initial setup wizard has other stuff for setting interface IPs, DNS servers and so on. So if someone sets their interface assignment from the console, we still want to present them with the wizard when they first login so they are prompted automagically to think about these other things.

patch fails on 2.3.3 and 2.4

2.3:

--------------------------
/usr/bin/patch --directory=/ -t -p2 -i /var/patches/58c039ad4acfd.patch --check --forward --ignore-whitespace

Hmm...  Looks like a unified diff to me...
The text leading up to this was:
|diff --git a/src/etc/inc/config.console.inc b/src/etc/inc/config.console.inc
|index bb2659e..1415e86 100644
|--- a/src/etc/inc/config.console.inc
|+++ b/src/etc/inc/config.console.inc
--------------------------
Patching file etc/inc/config.console.inc using Plan A...
Hunk #1 succeeded at 487 (offset 110 lines).
Hmm...  The next patch looks like a unified diff to me...
The text leading up to this was:
--------------------------
|diff --git a/src/etc/rc.bootup b/src/etc/rc.bootup
|index f33b434..60919e0 100755
|--- a/src/etc/rc.bootup
|+++ b/src/etc/rc.bootup
--------------------------
Patching file etc/rc.bootup using Plan A...
Hunk #1 failed at 138.
1 out of 1 hunks failed while patching etc/rc.bootup
Hmm...  The next patch looks like a unified diff to me...
The text leading up to this was:
--------------------------
|diff --git a/src/usr/local/www/wizards/setup_wizard.xml b/src/usr/local/www/wizards/setup_wizard.xml
|index 72363e2..ba6382a 100644
|--- a/src/usr/local/www/wizards/setup_wizard.xml
|+++ b/src/usr/local/www/wizards/setup_wizard.xml
--------------------------
Patching file usr/local/www/wizards/setup_wizard.xml using Plan A...
Hunk #1 failed at 35.
1 out of 1 hunks failed while patching usr/local/www/wizards/setup_wizard.xml
done

2.4:

/usr/bin/patch --directory=/ -t -p2 -i /var/patches/58c03ce3b281b.patch --check --forward --ignore-whitespace

Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|diff --git a/src/etc/inc/config.console.inc b/src/etc/inc/config.console.inc
|index bb2659e..1415e86 100644
|--- a/src/etc/inc/config.console.inc
|+++ b/src/etc/inc/config.console.inc
--------------------------
Patching file etc/inc/config.console.inc using Plan A...
Hunk #1 succeeded at 377.
Hmm...  The next patch looks like a unified diff to me...
The text leading up to this was:
--------------------------
|diff --git a/src/etc/rc.bootup b/src/etc/rc.bootup
|index f33b434..60919e0 100755
|--- a/src/etc/rc.bootup
|+++ b/src/etc/rc.bootup
--------------------------
Patching file etc/rc.bootup using Plan A...
Hunk #1 failed at 138.
1 out of 1 hunks failed while patching etc/rc.bootup
Hmm...  The next patch looks like a unified diff to me...
The text leading up to this was:
--------------------------
|diff --git a/src/usr/local/www/wizards/setup_wizard.xml b/src/usr/local/www/wizards/setup_wizard.xml
|index 72363e2..ba6382a 100644
|--- a/src/usr/local/www/wizards/setup_wizard.xml
|+++ b/src/usr/local/www/wizards/setup_wizard.xml
--------------------------
Patching file usr/local/www/wizards/setup_wizard.xml using Plan A...
Hunk #1 succeeded at 35.
done

The previous error was due to a CE patch being applied to a factory image. Renato created a factory patch and I was able to confirm that it resolved the issue.