I've got a server with multiple virtual interfaces. Now, I only want CUPS to advertise on *one* - eth0, not eth0:1 or eth0:gad....
Looking at the CUPS manual, and cuppsd.conf man page, I see BrowseAllow, but the entries are not clear enough for me to understand what they mean. (Yeah, I know the docs are better than they were - read ESR's rant about it from a few years ago.)
Specifically, I *think* I'd like to use BrowseAllow @IF, but I can't figure out if that should be BrowseAllow @IF(eth0) or BrowseAllow @IF(hostname)
Also, if it's interface name, and there are multiple virtual interfaces on eth0, and I use the first of the two lines, above, will that *not* also apply to the VIs on eth0?
mark
From: "m.roth@5-cent.us" m.roth@5-cent.us
I've got a server with multiple virtual interfaces. Now, I only want CUPS to advertise on *one* - eth0, not eth0:1 or eth0:gad.... Looking at the CUPS manual, and cuppsd.conf man page, I see BrowseAllow, but the entries are not clear enough for me to understand what they mean.
Wouldn't 'Listen <IP>:<PORT>' do what you want...?
JD
JD wrote"
From: "m.roth@5-cent.us" m.roth@5-cent.us
I've got a server with multiple virtual interfaces. Now, I only want CUPS to advertise on *one* - eth0, not eth0:1 or eth0:gad.... Looking at the CUPS manual, and cuppsd.conf man page, I see BrowseAllow, but the entries are not clear enough for me to understand what they mean.
Wouldn't 'Listen <IP>:<PORT>' do what you want...?
Hmmm, didn't see that one. Do you know if you can have more than one IP - I mean, it should listen on loopback, also.
mark
From: "m.roth@5-cent.us" m.roth@5-cent.us
Hmmm, didn't see that one. Do you know if you can have more than one IP - I mean, it should listen on loopback, also.
Yes, the CUPS Manual says: "Multiple Listen directives can be provided to listen on multiple addresses"
JD
From: "m.roth@5-cent.us" m.roth@5-cent.us
Hmmm, didn't see that one. Do you know if you can have more than one IP - I mean, it should listen on loopback, also.
Yes, the CUPS Manual says: "Multiple Listen directives can be provided to listen on multiple addresses"
Well, did that... and no joy, from another box, I can still telnet to the server on one of the virtual IPs, port 631. I can't really play around much, here - this is a production box, used by a lot of staff.
mark
From: "m.roth@5-cent.us" m.roth@5-cent.us
Yes, the CUPS Manual says: "Multiple Listen directives can be provided to listen on multiple addresses"
Well, did that... and no joy, from another box, I can still telnet to the server on one of the virtual IPs, port 631. I can't really play around much, here - this is a production box, used by a lot of staff.
Strange; I just created an alias on my PC, told cups to listen on my main IP, and it did...
eth0 = 192.168.16.23 eth0:0 = 192.168.16.40
# grep Listen /etc/cups/cupsd.conf Listen localhost:631 Listen 192.168.16.23:631 Listen /var/run/cups/cups.sock
# netstat -nltp | grep cupsd tcp 0 0 192.168.16.23:631 0.0.0.0:* LISTEN 18733/cupsd tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN 18733/cupsd
$ telnet 192.168.16.40 631 Trying 192.168.16.40... telnet: connect to address 192.168.16.40: Connection refused telnet: Unable to connect to remote host: Connection refused
Guess you restarted cupsd... right?
JD
-
John Doe -
m.roth＠5-cent.us