[CentOS] CUPS and virtual interfaces

2010-03-31 Thread m . roth
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 do

Re: [CentOS] CUPS and virtual interfaces

2010-03-31 Thread John Doe
From: "m.r...@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 understan

Re: [CentOS] CUPS and virtual interfaces

2010-03-31 Thread m . roth
JD wrote" > From: "m.r...@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 m

Re: [CentOS] CUPS and virtual interfaces

2010-03-31 Thread John Doe
From: "m.r...@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 ___

Re: [CentOS] CUPS and virtual interfaces

2010-03-31 Thread m . roth
> From: "m.r...@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 a

Re: [CentOS] CUPS and virtual interfaces

2010-04-01 Thread John Doe
From: "m.r...@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,