If you do not want to isolate your PCs from each other but simply have a "flat" network, then yes, a LAN bridge is the way to go. Don't expect too much performance-wise, though. OPNSense is not a switch and you might be better off getting a cheap but reliable gigabit switch and only connect one OPNsense LAN port.The LAN bridge is documented here:https://docs.opnsense.org/manual/how-tos/lan_bridge.html
Quote from: pmhausen on November 21, 2022, 05:00:37 pmIf you do not want to isolate your PCs from each other but simply have a "flat" network, then yes, a LAN bridge is the way to go. Don't expect too much performance-wise, though. OPNSense is not a switch and you might be better off getting a cheap but reliable gigabit switch and only connect one OPNsense LAN port.The LAN bridge is documented here:https://docs.opnsense.org/manual/how-tos/lan_bridge.htmlAhh, thanks! I'm trying to keep it to the firewall 2.5Gbps ports (both PC and NAS are 2.5). I'll see if I can snag a cheap 2.5Gbps port this black Friday. If not, I'll give my hand at bridging the ports. It's an i7 1165G7 so it's not a slow PC as far firewall standards go.
Just create a LAN bridge then following the documentation.
If you setup the LAN bridge the devices will be able to communicate with each other as if they were connected with a switch. The OPNsense does not have any say in that part of the communication.As soon as any device communicates with something that is on another interface (WAN probably) of the OPNsense you can of course apply QoS, Zenarmor, etc. based on the devices IP address or MAC address. You cannot setup policy per port because you have only one LAN "port" (the bridge).But that's how it's supposed to work.
Do you have "permit all in" rules on all your LAN ports? If yes, what's the point of not using a LAN bridge? If no, you need to explicitly permit all traffic you want to relay via UDP Broadcast Relay. Simply enabling the function does not change the firewall rules.