[cups.general] sharing configuration

[cedric briner]

> On Mar 13, 2009, at 1:52 AM, cedric briner wrote:
>> Hello,
>>
>> I'm trying to setup a cups system to serve at the best roaming laptop
>> and workstation.
>>
>> I'm having some problems here and there.
>>
>> 1) Some times, my cups server start to advertise with a 0 port instead
>> of 631.
> 
> That should never happen; can you post a link to your error_log file  
> with the LogLevel set to debug2?
the cups server advertize from cups-server:631 to cups-server:0 when I 
do a kill -1 <cups server pid>

Maybe this happens due to the strange configuration I have. The cups 
server has 2 ip addresses: 10.194.65.10(private) and 
129.194.65.10(public). The 129.194.6[4-7].x network can talk to the 
10.194.6[4-7].x because it is routed. So the cups server :
Listen 10.194.65.10:631
and not the 129.194.65.10:631

and the cups server has a BrowseAddress on 129.194.67.255 (that is the 
broadcast adress for our 129.194.64.0/22 network) and no BrowseAddress 
on 10.194.67.255.

I've check that this happens with wireshark for this error_log. To 
create this error log, I've done:

#remove old log
date
   Tue Mar 17 10:02:16 CET 2009
/etc/init.d/cups start
   Starting Common Unix Printing System: cupsd.
#verify that wireshark capture ipp trafic with cups-server:631
date
   Tue Mar 17 10:02:31 CET 2009
kill -1 <cups server pid>
#verify that wireshark capture ipp trafic with cups-server:0
/etc/init.d/cups stop
   Stopping Common Unix Printing System: cupsd.

the full data provided are on:
http://obswww.unige.ch/~briner/cups

there is also the cups server configuration into it:
   http://obswww.unige.ch/~briner/cups/cupsd.conf
I've copied the error_log into it :
   http://obswww.unige.ch/~briner/cups/error_log
and the wireshark data into it :
   http://obswww.unige.ch/~briner/cups/cups.wireshark

the wireshark capture filter (tcpdump alike) is:
   port 631 and src host 129.194.65.10
         the ip of the cups server /



> 
>> 2) How do you manage (by policies in cups or other), that a failing  
>> 3) Is there a good pointer telling how to configure iptables in  
thanks for the clear response.

cEd


-- 

Cédric BRINER
Geneva - Switzerland