Unable to print to IPP printer through linux firewall

Have been unable to print or ping printer through firewall from web.
Have tried enabling port forwarding to printer fixed ip to port 631 with
no success. Only by setting dmz to printer ip, does the printer work
over Internet. Iptables -L the following line is found.

ACCEPT tcp -- anywhere 192.168.1.2 tcp dpt:631

Any tips or tricks at command line to fix problem?

Joseph Wardzinski wrote:
> Have been unable to print or ping printer through firewall from web.
> Have tried enabling port forwarding to printer fixed ip to port 631 with
> no success. Only by setting dmz to printer ip, does the printer work
> over Internet. Iptables -L the following line is found.
>
> ACCEPT tcp -- anywhere 192.168.1.2 tcp dpt:631
>
> Any tips or tricks at command line to fix problem?
Forgot a line to post:
ACCEPT udp -- anywhere 192.168.1.2 udp dpt:631
Still doesn't work.

Joseph Wardzinski wrote:
> Joseph Wardzinski wrote:
>
>> Have been unable to print or ping printer through firewall from web.
>> Have tried enabling port forwarding to printer fixed ip to port 631
>> with no success. Only by setting dmz to printer ip, does the printer
>> work over Internet. Iptables -L the following line is found.
>>
>> ACCEPT tcp -- anywhere 192.168.1.2 tcp dpt:631
>>
>> Any tips or tricks at command line to fix problem?
>
> Forgot a line to post:
> ACCEPT udp -- anywhere 192.168.1.2 udp dpt:631
> Still doesn't work.

Maybe it's a problem of the cupsd daemon just listening to the
LAN or localhost IPs. Check it's configuration.

Regards.

--

Jose Maria Lopez Hernandez
Director Tecnico de bgSEC
(E-Mail Removed)
bgSEC Seguridad y Consultoria de Sistemas Informaticos
http://www.bgsec.com
ESPAÑA

The only people for me are the mad ones -- the ones who are mad to live,
mad to talk, mad to be saved, desirous of everything at the same time,
the ones who never yawn or say a commonplace thing, but burn, burn, burn
like fabulous yellow Roman candles.
-- Jack Kerouac, "On the Road"

Jose Maria Lopez Hernandez, mié20050223@11:05:53(CET):
>

:^P.


> Maybe it's a problem of the cupsd daemon just listening to the
> LAN or localhost IPs. Check it's configuration.

I don't think so. The default config behaves like this:

# netstat -putan|awk '/cupsd/ {print $1,$4}'
tcp 0.0.0.0:631
udp 0.0.0.0:631


--
David Serrano

Hue-Bond wrote:
> Jose Maria Lopez Hernandez, mié20050223@11:05:53(CET):
>
> :^P.

Hi!

> I don't think so. The default config behaves like this:
>
> # netstat -putan|awk '/cupsd/ {print $1,$4}'
> tcp 0.0.0.0:631
> udp 0.0.0.0:631

Sorry, but not in my Fedora Core 3, without touching anything
in the cups configuration, only the printer setup:

[root@nostromo correo]# netstat -putan|awk '/cupsd/ {print $1,$4}'
tcp 127.0.0.1:631
udp 0.0.0.0:631

Kind regards.

--

Jose Maria Lopez Hernandez
Director Tecnico de bgSEC
(E-Mail Removed)
bgSEC Seguridad y Consultoria de Sistemas Informaticos
http://www.bgsec.com
ESPAÑA

The only people for me are the mad ones -- the ones who are mad to live,
mad to talk, mad to be saved, desirous of everything at the same time,
the ones who never yawn or say a commonplace thing, but burn, burn, burn
like fabulous yellow Roman candles.
-- Jack Kerouac, "On the Road"

Jose Maria Lopez Hernandez, sáb20050226@20:43:21(CET):
>
> Sorry, but not in my Fedora Core 3, without touching anything
> in the cups configuration, only the printer setup:
>
> [root@nostromo correo]# netstat -putan|awk '/cupsd/ {print $1,$4}'
> tcp 127.0.0.1:631
> udp 0.0.0.0:631

Hmm, interesting. Just for google archives, mine is a debian sid.


--
David Serrano