Is this possible with Merlin? I don’t know where to start

[vmachiel]

Hi,

So I’ve got a BE86U running the latest Merlin. Basically, I want to isolate my work laptop (which is full of “corporate malware”) from the rest of my network. I think I have to create a new network with a different subnet for that right?

BUT: I want it to be able to acces 1 device on my main network: my raspberry pi running pihole. Is this doable with vlans/subnets etc? I’m not THAT tech savvy so I don’t know what to look for. If someone can point me in the right direction that would be awesome.

Thanks!

 

[bbunge]

Create a guest WIFI for the laptop. Install Diversion on the router and dump the Pi-Hole. Diversion does the same as Pi-hole and uses the same block lists.

 

[visortgw]

Create a guest WIFI for the laptop. Install Diversion on the router and dump the Pi-Hole. Diversion does the same as Pi-hole and uses the same block lists.

That depends on what block list(s) the PiHole uses. Couldn't the user explicitly point the guest network's DNS to the PiHole using DNS Director?

 

[bennor]

Basically, I want to isolate my work laptop (which is full of “corporate malware”) from the rest of my network.

If the laptop is connected via WiFi then create a Guest Network Pro profile and join the laptop to it. When creating the Guest Network Pro profile make sure to disable the option Use same subnet as main network.

BUT: I want it to be able to acces 1 device on my main network: my raspberry pi running pihole.

You can configure LAN> DNS Director to perform this step. DNS Director has a section for Guest Network Pro profiles where you can select the Guest Network Pro profile and assign a User defined DNS field to it. You would input the Pi-Hole's IP address into that User defined DNS field on the DNS Director page. There are likely more configuration one may need to do on the DNS Director page depending on one's use case. On the Pi-Hole you will likely need to change the DNS Settings > Interface Setting from Allow only local requests to Respond only on interface so the Pi-Hole correctly accepts DNS requests from the Guest Network Pro profile's IP subnet.

Edit to add: See attached example of how I have my Pi-Hole(s) configured under 3006.102.5 firmware on a RT-AX86U Pro. In my example the Guest Network Pro Profiles (two of them) use the Pi-Hole's IP address that is input into the User defined DNS #1 field.