Sharing Linux Printers Across Subnets - page 2
Printing Is Still Vexatious. But We Can PrevailSo my recipe for least pain is to edit cupsd.conf directly, and ignore all those goofy GUI thingies. Let's say you have two subnets, 192.168.1.0/24 and 192.168.2.0/24. You need to have routing already configured to pass traffic between the two subnets, so everyone can ping everyone. Let's say you have a printer server at 192.168.1.10, and you want computers on 192.168.2.0/24 to be able to use it. This is a complete, barebones example CUPS configuration for 192.168.1.10:
##/etc/cups/cupsd.conf LogLevel warning #this varies; check your distribution SystemGroup lpadmin # Allow remote users to access this server Port 631 Listen /var/run/cups/cups.sock # Enable printer sharing Browsing On BrowseAllow all BrowseAddress 192.168.1.255 BrowseAddress 192.168.2.255 DefaultAuthType BasicYou may use hostnames in place of IP addresses. Then restart CUPS, either /etc/init.d/cupsys restart on Debian-ish systems, or /etc/init.d/cup restart on Fedora/Red Hat-ish systems.
# Allow shared printing Order allow,deny Allow 192.168.1.0/24 Allow 192.168.2.0/24 # Only local users can access Web admin pages Order allow,deny Allow localhost # Only local system users can access config files AuthType Basic Require user @SYSTEM Order allow,deny Allow localhost
Your configuration may come with a batch of policy directives. You can leave these as they are.
- Skip Ahead
- 1. Printing Is Still Vexatious. But We Can Prevail
- 2. Printing Is Still Vexatious. But We Can Prevail
- 3. Printing Is Still Vexatious. But We Can Prevail
Solid state disks (SSDs) made a splash in consumer technology, and now the technology has its eyes on the enterprise storage market. Download this eBook to see what SSDs can do for your infrastructure and review the pros and cons of this potentially game-changing storage technology.