itpp21

You can do this by editing the backup and restore, as you have to change 2 fields at the same time via the GUI.YMMV and this hack is at your own risk.

Try updating the firmware to V2.60(AAHK.3) | 01/05/2021

pfSense is indeed a firewall.I've taken the 1900 in to production yesterday early and so far all good. For LAG1 it defaults to VLAN 1 and has 10 added so serving 2 vlans. The are no other switches in use, services are clustered to a port on the 1900 and then assigned a vlan when required, this vlan is then added as allow…

The way I've done it sounds like untag multiple vlans to multiple ports instead of assigning multiple tagged vlans to a port, which seems to work as intended (block traffic between vlans and allow one vlan to be shared), where one question remains: does this make sense?

Thats because you can't en-mass change vlan 1 to anything else as there are two places that needs changing and when one or the other is changed you loose (web) access (they need to be changed at the same time) so in my case VLAN 1 remained 1 instead of 20. Other segments will use 20 and higher after the 1900 is put into…

This works, though might not be as it should be configured, here it does the job (isolation port 6) Vlan config -> Goto ports ->Set port 6 to a different vlan (port 2 and 3 are LAG1) Goto Vlan Port -> Untag LAG1 for Vlan 10 (allow port 6 on vlan 10 to access LAN2WAN gateway) This works but I am open for improvements.

Hi Adam, > Do port 4 and 5 connect to the same device? if so, it should configure link-aggression as well. No, port 4 and 5 service different purposes. > but a port is only to allow one PVID Using PVID next to VLAN assignments is based on a remark that vlan(tagged) unaware devices need a PVID set on the port. If such…