upgraded to suse 9.2

printer via cups, but will only work if firewall turned off.

the printer is at lpd://192.168.1.100:515/L1

what must I do to suse firewall to let the printing work please?
this worked fine with the previous versions, (8.2, 9.0, 9.1)so they must have changed some setting

thank you very much

I would really appreciate an answer, as I have to turn the firewall off each time I want to print

thank you

Now I don't have 9.2, but if the interface is the same as 9.1, I think I can help.

Open YaST-> Security and Users -> Firewall. There will be several pages in a row. One of them will deal with the ports that are to be left open (not firewalled: http, ftp, ssh, smtp, and more). If lpd is not an option, then type 515 in the box provided. That SHOULD do it. That is what it is designed for. My machine has problems with this for some unexplained reason. Good luck.

the interface appears to be the same as on 9.1, but the way it works is different.

I have typed 515 into both the "additional TCP services" and/or the "additional UDP services" box with out any success.

If I switch the firewall off it prints fine.

the SUSE site appears to have no information about this.

Thanks,

This is what it says in mine. It should be easy. If it doesn't work in yours, then it sounds as if something is broken. For a more direct access to these settings, you can try looking in /etc/sysconfig/SuSEfirewall2. This file can also be manipulated in YaST-> System-> /etc/sysconfig Editor-> Network-> firewall.

If all else fails, turn off the SuSEfirewall2 and install another firewall program (or learn iptables yourself). Warning: you might have trouble doing this if you have more than one network card. They will sometimes detect in a different order and be assigned different names. You wont have this issue with just one card.

515 probably isn't the port, add these:
631 <- either the printer or the cups server
139 <- samba, network protocol for linux to and from windows
445 <- I forgot

you might need just 631

did this work?

no

http://localhost:631 works ?

yes, it works (i.e. in a browser window)

check /etc/cups/cupsd.conf (server side) and /etc/cups/client.conf (linux client side) yast recognize your cups printers?

in my /etc/cups/client.conf I add
# OVP
ServerName 192.168.1.10
# BXL
#ServerName 192.168.0.146
I change if my laptop is on an other place(OVP,BXL)in (not yet multi profile implemented, but I do in few time)
in my /etc/cups/cupsd.conf I add my 192.168 local network
<Location />
Encryption IfRequested
Satisfy All
Order deny,allow
Deny From All
Allow From 127.0.0.1
Allow From 127.0.0.2
Allow From 192.168.*.*
</Location>
<Location /admin>
AuthType Basic
AuthClass System
Encryption IfRequested
Satisfy All
Order deny,allow
Deny From All
Allow From 127.0.0.1
Allow From 192.168.*.*
</Location>

yes, yast does see the cups printers, & even if I reconfigure the printers through yast, it still won't print unless the firewall is turned off....

have altered my cups conf as you suggested.

if firewall is off

nmap 192.168.1.100 gives

PORT STATE SERVICE
23/tcp open telnet
80/tcp open http
139/tcp open netbios-ssn
515/tcp open printer
631/tcp open ipp

however with firewall on (and the above ports kept open in "expert" settings & cups conf allowing as you suggested)

Starting nmap 3.70 ( http://www.insecure.org/nmap/ ) at 2004-12-29 12:37 GMT
Note: Host seems down. If it is really up, but blocking our ping probes, try -P0
Nmap run completed -- 1 IP address (0 hosts up) scanned in 4.005 seconds

So it appears that the "expert settings" in the Suse Firewall are not doing their job.

any other ideas anyone????

thanks

well, as far as I have used suse's firewall it appears to me they only block traffic between the internal and the external interface.

that is if your computers and printers and what not are internal and internet (e.g. dsl with dsl0) is external the firewall should not even see what is going on.

if you want to have different subnets you might try ip aliasing to use one network card in 2 subnets.

lets say your computers are within the 192.168.0.xxx subnet
and the printers + router and so on are 192.168.1.xxx

you could set up something like this

this will give you an additional network interface eth0:0

so your pc connets to a switch, so does the router.
the pc is 192.168.0.1 and lets say 192.168.1.5 at the same time. via the switch it can access both the 192.168.0.xxx (directly) and via the router the 192.168.1.xxx machines.

you'd still have to take care of the routing table though...
and keeping it all inside just one subnet is easier anyway.

my config:

pc 192.168.0.4
printserver 192.168.0.2

works just fine with suse 9.2