Prev: Sequence Diagrams from Packet Analyzer logs/output files - Free
Next: raw sockets & security in Linux
From: Fguy on 5 Jan 2010 09:19
OK first I refer you to this old thread from a few months ago. I would
have preferred to revive that thread but there was no option to add a
reply.

http://groups.google.ca/group/comp.os.linux.networking/browse_thread/thread/a94976f3eadef857/cf3dc9f9d780c7f0#cf3dc9f9d780c7f0

To summarize, the thread deals with some TCP/IP confiuration steps
required to establish lpr printing from Windows XP Professional to
Debian Lenny on a wireless network. I am talking the old BSD style
lpr, not CUPS. I know there are probably better ways to print, I just
like to cover all my bases from a learning perspective.

OK, there were two key issues to enable TCP/IP for LPR. One step was
a change to the lpd startup script so that lpd would listen on a TCP/
IP socket and not a UNIX domain socket. No problem there.

The issue I would like to discuss is as follows. In order to get
things working, I had to create a file called /etc/hosts.lpd , and in
that file just specify the host name of my Windows box. Then I had to
add a line to /etc/hosts specifying the name and ip of the Windows
box. Note that just specifying the ip address in hosts.lpd did not
solve the issue. Furthermore not that nothing was added to hosts.allow
for this purpose.

This all seems like a strange way to have to do things. I would not
want to have to edit two host files for every workstation that wanted
to use the lpr service. Is there a better way to deal with these TCP/
IP issues?

Perhaps I have touched upon the reason why BSD style lpr is the old
way to do things?

Thanks.
 | 
Pages: 1
Prev: Sequence Diagrams from Packet Analyzer logs/output files - Free
Next: raw sockets & security in Linux