@[email protected] to TechnologyEnglish • edit-25 hours agoBrother accused of locking down third-party printer ink cartridges via forced firmware updates, removing older firmware versions from support portals [see comments]www.tomshardware.comexternal-linkmessage-square205fedilinkarrow-up11.13Karrow-down14file-textcross-posted to: hardware[email protected][email protected]
arrow-up11.13Karrow-down1external-linkBrother accused of locking down third-party printer ink cartridges via forced firmware updates, removing older firmware versions from support portals [see comments]www.tomshardware.com@[email protected] to TechnologyEnglish • edit-25 hours agomessage-square205fedilinkfile-textcross-posted to: hardware[email protected][email protected]
Brother deny the claims: https://arstechnica.com/gadgets/2025/03/brother-denies-using-firmware-updates-to-brick-printers-with-third-party-ink/ via https://startrek.website/comment/15279250
minus-squareLuffylinkfedilinkEnglish8•18 hours agoJust connect it to a Server (like a raspi) via USB and share the printer through CUPS Its a little tedious to set up, but it works
minus-square@Nevermore9197linkEnglish3•11 hours agoIs there a step by step anywhere to achieve this? I’m adept in tech. But don’t have the training or knowledge to just do it
minus-squareivanafterall ☑️linkEnglish7•14 hours agoHow many cups does it take to transfer the printer over?
minus-square@_apokalipto_linkEnglish3•11 hours agoI think you can just use 1 large bucket instead of many small cups. Faster that way.
minus-square@[email protected]linkfedilinkEnglish1•16 hours agoWhy do that when you could just connect it to the LAN and put it on a separate VLAN?
minus-squarenickwitha_k (he/him)linkfedilinkEnglish1•3 minutes agoBecause the built-in networking stack on printers is garbage and having to install drivers on every client sucks.
minus-square@[email protected]linkfedilinkEnglish4•13 hours agoBecause it’s a lot simpler and avoids the issue of dealing with printer drivers on all your machines.
minus-square@[email protected]linkfedilinkEnglish2•edit-213 hours agoI could see the argument that it’s more air gapped this way. Without having physical access to the Pi (or at least SSH access), it’d be hard to get any network connection through USB. But personally, I just blocked outgoing traffic from the printer.
Just connect it to a Server (like a raspi) via USB and share the printer through CUPS
Its a little tedious to set up, but it works
This is the way.
Is there a step by step anywhere to achieve this? I’m adept in tech. But don’t have the training or knowledge to just do it
How many cups does it take to transfer the printer over?
I think you can just use 1 large bucket instead of many small cups. Faster that way.
Why do that when you could just connect it to the LAN and put it on a separate VLAN?
Because the built-in networking stack on printers is garbage and having to install drivers on every client sucks.
Because it’s a lot simpler and avoids the issue of dealing with printer drivers on all your machines.
I could see the argument that it’s more air gapped this way. Without having physical access to the Pi (or at least SSH access), it’d be hard to get any network connection through USB.
But personally, I just blocked outgoing traffic from the printer.