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:
- 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.
- 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.
- 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!
Hi all, thanks for all your comments and suggestions, here’s a late update:
I went with option 2 and configured the second VLAN + Wifi with the printer on it. The process was smooth except for half a day troubleshooting why DHCP was not possible (turns out I have to manually tell dnsmasq to listen on the new interface as well…). I set up a static IP address for the printer though. Adding the machine from my other devices involve manually typing out its IP, something I hope to resolve with an avahi daemon on the router later on.
For Android specifically, printing can be configured through its “Default Print Service” which can be found in Settings. Scanning requires a separate app, and I found ScanBridge to be exactly what I need and also FOSS. The address to type in is
http://$PRINTER_IP_ADDRESS/eSCL/(note the trailing slash). There’s also Mopria Scan, which is proprietary.If you use a VPN on the Android, remember to exempt the print service and scan app from the tunnel.
I use a VLAN that blocks it from my WAN interference.
All internal VLAN except my Internet only VLAN can print to it.
Point at it and tell it to go to time out in front of everybody.
Seems you can actually use the openwrt router as a non spooling print server if you want.
I wouldn’t recommend it for multi user due to lacking the spool queue but kinda cool:
https://openwrt.org/docs/guide-user/services/print_server/p910ndprinterserver- sounds like it should be enough for your needs and simple to admin too.
VLANs. You create an IoT VLAN, set it to be accessible the specific way you want, and you’re done.
If you want to be extra secure you can fire up a Docker container that sits on this VLAN + your regular network, and proxies printer requests between the two, so you have perfect control over what happens and when.
Fair note, none of the apps (e.g. AirPrint) will work this way. They use Brother’s cloud to connect to the printer.
FWIW, I use the VLAN approach. I have a VLAN (101) specifically for IoT shit. The firewall allows devices on other VLANs - general purpose (104), infrastructure (102) and servers (103) to connect in to 101, but nothing can reach out. Works seamlessly. The only issue you might bump into is that some devices use UPnP/mDNS for discovery, but OpenWRT has a proxy module you can install to facilitate that.
You may be wondering why the tags I use for my VLANs are so odd. I also wonder that sometimes.
Are those also the aame subnet or in different network (e.g. 192.168.101.0/24 and 192.168.104.0/24)?
Different subnets, similar to how you describe. It would be really tricky to have them on the same subnet, especially if you want a firewall between them.
Static ipv4, don’t set a default gateway, or set the wrong gateway if it doesn’t accept blank fields… Quick and easy
FWIW, I have a networked Brother laser printer hard-wired to my LAN. To prevent it from calling home or pulling unfriendly firmware “upgrades”, I just configured it with a static LAN IP & subnet, but no gateway address. Been running that way for years now. So far so good…
Anything dealing with printers generally requires at least a basic understanding of eldritch magic.
Too true. I’ve spent more late nights arguing with CUPS than everyone I’ve dated in my whole life.
At this point when I start mumbling expletives at the computer my wife just asks “Printer?”
Does she also ask you anytime she wants something printed? Mine does!
I saw a DIY open-hardware printer somewhere recently that uses a long butcher paper style paper roll and ink tanks. I’m intrigued. I don’t really use all the smart printer functions anyway.
Her computer tends to print more reliably than mine, so I usually ask her.
I fight my computer about once a month when it decides to have an aneurysm and forget how printers work.
You’re overthinking this with 2 & 3. All you need is to block all Brother Internet traffic.
Set up a static DHCP IP for the printer in Openwrt and create firewall rules to drop all WAN packets to/from that IP.
If you want to see evidence those packets are being dropped in real time use tcpdump. When watching LAN traffic you will see the printer sending packets to the WAN interface (they won’t get there) but will never see a response directed back to the printer.
I have a Brother printer (plus cameras & TVs) and an Openwrt router set up that way and have had zero issues.
Long term, 2 is best, but 1 is a great immediate fix. Also, you should be able to assign a static IP based on the printers MAC address, which will keep the IP stable.
I wouldn’t recommend isolating it as it will make it a pain to print.
You don’t need their proprietary app. Brother printers support driverless printing so it will work on all major platforms
If the point of connecting it to WiFi is to make it easier to print then why would you isolate it only to make it harder to print?
If you want 100% no sneaky stuff connect it to some PC and set up a cups server on it.
If you just want to stop it from having internet access then a firewall rule set to block from the printer IP, and dest !=LAN would do it.
For IP changes you just need to make that lease static in OpenWRT and it will be fixed to that IP going forward.
It basically depends on whether you want to rely on mdns, like printing from your phone.
The standard lock down by making a vlan and subnet and then adding filtering works fine if you can reach the printer reliably by IPP or jetdirect.
Once you need to connect two disparate broadcast domains, things get weird. It was the same story for Chromecast devices for me, their functionality and convenience are based on a relatively flat network and a single broadcast domain.
I did #2 and it works perfectly. I have an IoT VLAN and my Brother printer/scanner is on it. I pivoted to the Ubiquiti/Unifi network infrastructure several years ago due to mostly seemless integration with the routers/switches/APs. But have used OpenWRT in the past (but didn’t set up VLANs then). Not sure the steps and if it requires manual firewall rules for the VLAN in OpenWRT.
In case there identical/similar options to Unifi, however, I’ll just mention it’s pretty simple. Create the VLAN (new subnet vs the default network, e.g. 10.0.0.0/24 vs 10.1.0.0/24), deselect the “allow internet access” option, and make sure to select “network isolation” option (which blocks it from speaking to other VLANs/subnets). That’s it. (For conveniences, I also created another Wifi network call “XYZ_IOT” and then connected the printer to it. The network is fixed to that new IoT VLAN).
Technically, those options are effectively convenient shortcuts for firewall rules that will get removed or created, accordingly, for that specific VLAN.
Takes longer when you’re uncomfortable or struggling through it, but the complete setup time took maybe 15-20mins. If OpenWRT doesn’t have those convenience shortcuts, might take a bit longer to search for example firewall rule configs online and then make them.






