From: "Stephen Isard" <y8ju2p902@sneakemail.com>
To: netfilter@vger.kernel.org
Subject: iptables rules for cups printer discovery
Date: Thu, 14 Aug 2008 14:51:49 -0400 (EDT) [thread overview]
Message-ID: <19894-78618@sneakemail.com> (raw)
I'm wondering whether there are iptables rules that will permit cups
snmp printer discovery to operate without creating a serious security
risk.
Cups printer discovery works by sending a broadcast from a high numbered
port (a different one each time) to the snmp port (161) of every device
on the local network. Printers are then supposed to send back replies
from their port 161 to the high numbered port on the computer that the
broadcast came from. Since the replies are to a broadcast, they are not
treated as ESTABLISHED or RELATED by iptables rules. My question is
really whether there is some way of identifying replies to such a
broadcast, so that I don't have to let through all udp packets from port
161 of any machine on the local network to all high numbered ports on my
machine, at any time, which looks as if it might be unsafe, especially
when I can't be certain that the local network is absolutely secure
against break-ins.
Thanks.
next reply other threads:[~2008-08-14 18:51 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-14 18:51 Stephen Isard [this message]
2008-08-14 20:00 ` iptables rules for cups printer discovery Jan Engelhardt
2008-08-14 20:23 ` Stephen Isard
2008-08-14 20:37 ` Jan Engelhardt
[not found] ` <11653-43715@sneakemail.com>
[not found] ` <alpine.LNX.1.10.0808141744490.18538@fbirervta.pbzchgretzou.qr>
2008-08-14 23:01 ` Stephen Isard
2008-08-15 1:35 ` Grant Taylor
2008-08-15 1:53 ` Jan Engelhardt
2008-08-15 2:00 ` Grant Taylor
2008-08-15 2:04 ` Jan Engelhardt
2008-08-15 2:14 ` Grant Taylor
2008-08-15 2:26 ` Jan Engelhardt
2008-08-15 13:10 ` Stephen Isard
2008-08-15 13:23 ` Jan Engelhardt
2008-08-15 14:17 ` Stephen Isard
2008-08-15 15:21 ` Grant Taylor
2008-08-15 15:38 ` Stephen Isard
2008-08-15 16:16 ` Grant Taylor
2008-08-15 16:28 ` Stephen Isard
2008-08-15 18:01 ` Grant Taylor
2008-08-15 15:16 ` Grant Taylor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=19894-78618@sneakemail.com \
--to=y8ju2p902@sneakemail.com \
--cc=netfilter@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox