Hi all, I’ve gotten a Brother machine (DCP series) that can do wifi printing/scanning over their proprietary app. However, I’d like to lock it down from my network, because having it on the same LAN as my other devices and the ability to phone out to the internet seem like room for mischievious activities.

For context, I have OpenWRT on my router, and my clients can access the Brother using their iPrint&Scan app and AirPrint on wifi, as well as the traditional USB port. But I’m not good in networking. In my research, I drafted out the following solutions:

  1. Create a firewall rule to block the printer itself from making outbound requests. Seems simple, but I’m not sure if this can persist after IP changes or not.
  2. Create a VLAN for “IoT devices” that cannot send outbound requests to my normal VLAN nor the internet. Inspiration from this video, I’d need to manage a new SSID but it may come in handy for more IoT devices later.
  3. Hook the Brother up to a Raspberry Pi via USB, and install CUPS + SANE on the Pi. Assuming the Pi cannot “phone home” on behalf of the printer, this makes it a local-only “print+scan service” on my normal network and doesn’t require an extra VLAN.

I’d like to ask: which solution above is best for “neutering” the Brother? Or are there any alternatives/details I might’ve missed? I’m not sure if blocking outbound requests this way is enough of a security hardening for an untrusted device, and if there are any usability issues I’ve overlooked so far.

Thanks for any advice, and please share any printer/scanner setup you have in your networks as well. So hopefully I can get more inspiration!

  • Lære@quokk.au
    link
    fedilink
    English
    arrow-up
    2
    ·
    3 hours ago

    I do 1.
    I have DHCP but everything static gets a static IP. I need my home assistant to be able to reach both the internet and my IoT device, no idea how I’d put it in both VLANs.

    • djdogfart@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      2 hours ago

      In a similar situation, my theory is that I can eventually configure ACLs specifically to accept connections sourced to my IOT static IP assigned devices with an implicit deny all that prevents everything else.

      Though, I may be planning this all wrong, since all connections occur after my firewall, I might need to eventually set up ACLs on my smart switch.