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.
1 is enough if the hardware manufacturer is currently trustworthy at the time you put the firewall rules in place. Brother is AFAIK trustworthy. I have a Brother printer which is on my main network with no special firewall rules, but my printer is old enough to drink. It never connected to any cloud services and could never update itself to introduce new anti-features.
For both 2 and 3 you probably want a Raspberry Pi or other server to make the printer accessible to devices on your main network. Unless it’s a Facebook or Amazon or LG printer or something you should be fine with just 1.
What’s your concern with a new printer? In case 1, once set up and working how is a company going to introduce malicious features when the printer has absolutely no Internet access?
New printers can be okay. I don’t know of any specific problems with new printers except those ones with the ink subscription services. I’m saying my printer is old because it’s from another time. The only reason you’d isolate your networked printer in 2005 would be if you didn’t want other people to access your printer. Devices in your home automatically, deliberately making themselves worse on command from a cloud service was not a thing. The biggest danger with devices this old is that they probably have unpatched security vulnerabilities exploitable by anything else that gets on your network.
I have a VR headset from Facebook that is on its own VLAN because it defaults to randomizing its MAC address by default and this allowed it to bypass the firewall, phone home, and nonconsensually install new anti-features after being blocked because the setting got reset back to random when changing something. Recent LG TVs and other devices with worse preinstalled malware have been known to make requests to other devices on your network, but I’ve never heard of them using those other devices to get around network restrictions, at least not directly.
I have a VR headset from Facebook that is on its own VLAN because it defaults to randomizing its MAC address by default and this allowed it to bypass the firewall, phone home, and nonconsensually install new anti-features after being blocked because the setting got reset back to random when changing something.
That is infuriating and I’d do the same.
Plenty of reports of devices like LG TVs acting as gateways to external devices and LG in particular seems to be a privacy nightmare. I bought a couple of appliances that advertised their smart features only to find LG’s app was required. That app actually required both Internet access AND my exact location at all times to function at all! I shut it all down and disconnected everything from wifi.
You may be right to be concerned even about printers though. At some point we’re going to be reading about some built-in AI hacking other network devices for Internet access and transmitting our private information to the world.
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.
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.
Dst LAN is not required either. Assuming SPI.
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.
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.
If it’s a networked printer it needs to be able to broadcast to the LAN if you want IPP to work – which you probably do, since it’s well supported by all OS and lets you autodiscover the printer and print directly from most of your devices.
This means you can’t isolate it fully from the LAN, so solution 2 is out.
Solution 1 is good if you can trust the thing not to change or disguise its MAC address. I’ve heard of devices that have a 3rd dynamic MAC in addition to the wifi and ethernet MACs, that they use to bypass such restrictions. 🤪
In order to do (1) properly you should create a firewall zone specifically for the printer, and allow that zone access to LAN but deny access to WAN. Then associate that zone with either a wifi access point created specifically for the printer, or with a specific switch plug if connected via Ethernet. This way the printer can’t bypass the restriction because it comes packaged with the only way it has of getting any connectivity.
However OpenWRT firewall zones also have issues with cross-zone broadcast, but can be bypassed I think by installing and using Avahi on the router. Don’t quote me on that.
Solution 3 seems best if you want to fully isolate it as well as retain IPP capability. That’s what I did with my printer, I connected it with USB to the server and I run CUPS + Avahi in a docker container that uses an ipvlan network to broadcast.
Your comment about #2 is not true. VLANs can be fully isolated from other subnets on the LAN - sure. But they can also NOT be isolated. I have one fully isolated VLAN, and the rest are not isolated.
With a savvy user, you can also tehnically isolate VLANs form only specific other VLANs. I’ve never needed to do this, but know it’s possible.
Edit: for reference, I looked up details and found a helpful link and example:
config zone option name 'lan' option input 'ACCEPT' option output 'ACCEPT' option forward 'ACCEPT' <-- This line allows intra-zone (inter-subnet) routing list network 'lan' list network 'your_new_vlan' <-- Adding your new VLAN here stops it from being isolatedDamn, I didn’t know devices do these dynamic MACs, but yeah it’s not a trusted field to begin with.
By IPP autodiscovery, do you mean mDNS? If so, does the router needs to install avahi as well for single-network discovery to work? Or just the client?
Avahi on the router for multi VLAN discovery seem to be a nice idea, I’ll look into it and maybe try to hook it up to solution 2. I’ve thought users could just manually input the IP addresses (and the non-tech users will just simply be onboarded by me anyways), but having it advertised by default may just be less of a hassle for them.
IPP is a universal printer protocol aka “print anywhere”. Some printers support it natively, some need some help from a PC. If that PC runs Linux the most likely method is to run CUPS and connect it to the printer over USB.
By IPP autodiscovery, do you mean mDNS? If so, does the router needs to install avahi as well for single-network discovery to work? Or just the client?
Yes the autodiscovery is done with mDNS, which on Linux is done with Avahi.
Typically Avahi is needed if you consume services over mDNS or provide them.
So the Linux clients need Avahi. But the router only needs Avahi if the printer is connected to it, or to propagate broadcasts across zones.
I’ve thought users could just manually input the IP addresses
You can, but it’s really nice to have the printer available automagically (on any OS).
BTW one extra potential benefit of solution 3 might be that the “printer” would always appear to be present on the network and accept print jobs, even if the actual printer is off, because the Pi running the print server would actually be on. Otherwise if the printer itself is providing the connectivity and announcement it will not appear in the list when it’s off. Whether you consider this a plus or not depends on how you handle your printers, I turn mine off when not in use, but some people let it go into powersaving mode so it’s always ready to print.






