Migrate vlan to a different nic card
-
Is there a way to move a vlan that is on nic card A igb1 to nic card B igb4 with minimal interruption?
Thanks
-
@Hoser7632 what interruption would be acceptable? And what else in on igb1 right now? Any other traffic on igb4 already?
-
@patient0 I'm looking for the least interruption as possible and igb1 contains wifi vlan 4, and no traffic on igb4 currently.
Best Regards
-
@Hoser7632 said in Migrate vlan to a different nic card:
@patient0 I'm looking for the least interruption as possible and igb1 contains wifi vlan 4, and no traffic on igb4 currently.
Best Regards
Word of “caution”: I have from time to time experienced unpredictable behaviour when moving a VLAN from one interface to another requiring a reboot to be resolved. Mostly it just works, but there is a minor probabilty of a reboot required.
-
@keyser Yes I.ve read about that but how is it done?
-
@Hoser7632 I’m not quite sure you can do it fast/efficient via the UI because that has a “sequential” way of doing things that prbably will require you to unassign the interface to actually change the VLAN.
I have always done it using the serial console and using the assign interfaces menu because that allows you to assign both VLAN and interfaces in one long “questionaire” and then commits the assignment (but does not reboot the firewall).
But VPN tunnels and most services will reload in the process because the interfaces are “technically” reassigned. -
@Hoser7632 So I don’t know if the console is actually the best method, because while it is “fast” - the reload only takes maybe 10 seconds - it does affect all interfaces. If it can be done in the UI, you may be able to only actually disturb the interface being moved.
-
@Hoser7632 said in Migrate vlan to a different nic card:
@keyser Yes I.ve read about that but how is it done?
You edit the VLAN (Interfaces / VLANs) and change the parent interface. That does work for me, didn't matter that the VLAN is assigned to an interface.
But having said that: never done in production and sometimes a reboot is required.
If your pfSense is in running in a business and are talking seconds, then I don't know what the success rate is.
If it's a home setup: backup the config, make sure you access pfSense not from the VLAN, change the parent interface. In case of error, restore the config.
All the above assumes that you have connected a cable to igb4 and configured the connected switch for VLAN4 traffic correctly.
-
@patient0 Not a production environment just home environment. Thanks for your suggestion I'll give it a try.
Best Regards and thanks again....
