Access to other Vlans
I have two vlans, vlan 100 192.168.2.x and vlan 200 192.168.3.x
Also have my desktop on default vlan 1 192.168.1.x
My printer is on vlan 200 and I can't print from my desktop.
Is there a way to set a firewall rule to allow access to vlan 200?
For starters, VLAN 1 is untagged which means it can only communicate with other switch ports configured for VLAN 1. You need to create another tagged VLAN (e.g. 300) to put your desktops on.
^ what??? He does not need to create any other vlans? his untagged vlan 1 or "lan" can talk to other tagged vlans just fine..
I assume your vlan 1 or untagged is your LAN, and your other vlans you created are on the this lan physical interface - correct?
The default lan rules of any any would allow anything on the lan to talk to any opt/vlan network - the rule is any any ;)
When you say you can not print… This means what exactly? Your desktop is not finding the printer when you search for it? Can you ping the printers IP? Have you messed with the default lan rules your desktop is on?
Your switch that is connected pfsense interface is smart, and you have setup trunked port to pfsense where your vlan 1 (lan) is untagged and 200 and 100 are tagged. And then the ports on the switch where devices connect to 100 or 200 are untagged for those vlans? Your other devices can see pfsense IP in their vlan?
Bah, look at the turn this has already taken. We started with a flawed design and lack of information, so taking the OP down rabbit holes at the beginning (which he may or may not even understand) will just get messy, confuse everyone and triple (if not quadruple) the length of this thread.
Why go there? Why not address the flawed design to start with? You know very well he shouldn't be using VLAN 1 for data, we don't know if his LAN interface is addressed, no network map was provided so we don't' know how things are connected, we don't know what default GW is being used, we don't know if the connection to the switch is trunked, we don't know if the switch is even managed, etc, etc.
OP, IMO you should address your design before we go any further or it will add several days (if not weeks) to this thread.