Some questions about rule weirdness.
Firewalla Gold Pro (10 Gbps) + AP7 + MSP Pro.
First, my simple situation: I have an IoT VLAN.
A rule prevents devices from interacting with other devices in the VLAN (and other networks, etc).
I want to specify a rule to allow two specific Amazon Echo devices to see and interact with each other so each can take one side of a stereo arrangement when playing music. This has worked, but suddenly stopped. I realize the devices can't communicate directly across the network.
They both have reserved IP addresses and are connected to the AP7.
I begin to create a rule:
Name: Echo Stereo Music Negotiation
Action: Allow
Matching: Echo 1 IP address. (My only viable options are IP address or domain.)
On: ??? I can choose from groups, networks/vlans, or devices, but neither device is listed. Am I just supposed to create a group for this? If so, is that not a hacky work around? What's going on here? It's amazing I haven't run into this issue until now.
1) Why do some devices, that are absolutely online and connected to the Firewalla device through a switch or the AP, not show up in the devices list of the second part of the rule, in the drop down? I've noticed this applies to several devices on my network, but haven't been able to identify any rhyme or reason in what's available and what isn't.
2) Why doesn't Firewalla simply allow specific device selection as an option in the "Matching" field? Once you set up all of your zero trust rules and want to punch specific exceptions through the firewall with precise rules, it seems like that'd be the most painless, obvious way to build a lot of those rules, UI-wise.
Please sign in to leave a comment.
Comments
0 comments