I don't know if it's a coincidence, but I updated from GUI to version 26.1_4, and after about 30 minutes of not being able to connect, I went directly to the physical firewall and saw that it changed the order of the interfaces, which consequently disabled the various VLANs. I gradually fixed it and flagged prevert remove, also because this interface problem occurred even after I fixed it and restarted the fw.
So the question is which volatile network device/tunnel did you assign as an interface?
Cheers,
Franco
The problem was that it reversed the assignments of the physical interfaces, my configuration is igb0 WAN and igb1 LAN and all the vlans are parents of igb1. The strange thing is that I reassigned the interfaces, reset the vlans (it didn't delete them but only unassigned them) and when I rebooted I found igb0 LAN igb1 WAN
... which only happens when you assign an interface that moves it's location upon reboot or is not there during early boot?
Cheers,
Franco
Let's say it did the same as assigning standard interfaces during the first firewall installation, and the strange thing is that it did it even after I set the interfaces. I rebooted the system and found the new standard interfaces. Obviously, the VLANs were not visible for association, but from the GUI they were present waiting to be assigned.
So you created VLANs via ifconfig on the command line?
Cheers,
Franco
I not create the VLANs, via GUI the VLANs were already present but not assigned and I was able to reassign them after changing the LAN on igb1 and the WAN on igb0.