Communicating between LANs (Firewalla Gold)

I'd like to separate my wireless and wired devices into different LANs (I'd really like an IoT VLAN, but I use eero for my WiFi and it doesn't support VLANs). I've got my eero gateway plugged into 1 port, and the unmanaged switch that feeds my ethernet ports around the house plugged into another port. I've figured out how to create the second LAN. But I don't understand how to use rules to allow communication between them.

E.g., I'd like to use the Pi-holes (wired) with the wireless LAN. But even if I put the Pi-hole wired LAN address (192.168.1.x) into the LAN DNS fields for the wireless LANs (which is using 192.168.100.x) and create a rule that lets me access the Pi-holes from a wireless device (my iPhone), the wireless device won't use the Pi-hole for DNS.

Similarly, I'd like for certain wireless devices (iPhones, Macs) to be able to talk to my wired NAS (and vice versa). Not at all sure how to make a rule (or series of rules that would allow for that limited communication across the two LANs.

I'd also like all the wired devices to be able to talk to all of the wireless devices, but not vice versa.

Long and short is that I've having trouble understanding the rules settings for this set up -- any help would be greatly appreciated.

Scott Angstreich

August 26, 2020 00:41

An update:

I can get the wireless devices (192.168.2.x IP addresses) to use the wired Pi-holes (192.168.1.x IP addresses) if – but only if – I turn DNS booster off.

My wired devices reach the Pi-holes even with DNS booster on.

Is this expected behavior?

Saeed miam

August 29, 2020 20:56

The other messages from the hacker in your eyes first time leaving you a message

-1

August 29, 2020 20:57

I see there's a bunch of different messages and other stuff sahec is knows quite a bit

Communicating between LANs (Firewalla Gold)

Comments

Didn't find what you were looking for?