View Single Post
  #2   (View Single Post)  
Old 2nd March 2011
J65nko J65nko is offline
Administrator
 
Join Date: May 2008
Location: Budel - the Netherlands
Posts: 3,505
Default

I still have these notes I wrote down 4 years ago. But I think my situation was a little bit different then yours, so I am not sure it will help

Quote:
I installed apsfilter on a local OpenBSD box with an USB HP deskjet printer so it could be my print server.

The host name of the print server is 'protogoras.utp.xnet'.
To be able to print from my OpenBSD workstation "zeno.utp.xnet' I have this /etc/printcap
Code:
j65nko@zeno[~]cat /etc/printcap

#       $OpenBSD: printcap,v 1.4 2003/03/28 21:32:30 jmc Exp $

#lp|local line printer:\
#       :lp=/dev/lp:sd=/var/spool/output:lf=/var/log/lpd-errs:

lp|rp|remote line printer:\
        :lp=:rm=protogoras.utp.xnet:rp=lp:sd=/var/spool/output:lf=/var/log/lpd-errs:
On 'protogoras.utp.xnet' I have added ""zeno.utp.xnet'" to the file /etc/hosts.lpd.
Code:
j65nko@protogoras[~]cat /etc/hosts.lpd
#       $OpenBSD: hosts.lpd,v 1.2 1996/07/20 00:28:28 deraadt Exp $
# as described in lpd(8), place one legal access hostname per line
zeno.utp.xnet
On both the workstation and the print server I have enabled lpd
Code:
j65nko@protogoras[~]grep lpd /etc/rc.conf.local
lpd_flags=""
Please note this part of the lpd(8) man page
Code:
     lpd performs reverse DNS lookups on network clients.  If a client host-
     name cannot be determined from its IP address, the print request will be
     silently dropped.  This is important to note when debugging print prob-
     lems in dynamic address environments.
__________________
You don't need to be a genius to debug a pf.conf firewall ruleset, you just need the guts to run tcpdump
Reply With Quote