From: Chris <mlists@aon.at>
To: netfilter@lists.samba.org
Subject: Allowing limited broadcasts between LAN <-> DMZ?
Date: Tue, 25 Jun 2002 11:27:56 +0200 [thread overview]
Message-ID: <3D18379C.B101AA83@aon.at> (raw)
In-Reply-To: Pine.LNX.4.33.0206251044140.4927-100000@blackhole.kfki.hu
Hello,
i am wondering if it would be a security risk to generally allow ALL
limited broadcasts (255.255.255.255)?!
We have a heterogenous network with Linux (Firewalls, Mail/Proxy/Time/
etc-server), WinNT/W2k Clients & Servers and one AS/400 as server.
Now there is our internal firewall between the LANs and the DMZ.
At the moment i am blocking limited broadcasts, which breaks the
functionality of some windows stuff (SQL-Server, NetBIOS, SMB, ...).
So i allow this traffic "manually" with adding according rules to the
internal firewall.
Why am i blocking the limited broadcast? Because i was sniffing around
and found several "example scripts" which do this. The question is
if this is REALLY necessary and if someone could exploit a not blocked,
limited broadcast?
Just yesterday we connected a printer to our LAN, and now it is sending
limited broadcasts to UDP port 123?!? (it want's to know the time?? :))
However, it's kind of annoying to see those entries in the logfile now
every five minutes.. sure i could allow/drop this without logging,
but the question is - again :) - can't i just allow ALL limited broad-
casts on the internal firewall?
regards, Chris
next prev parent reply other threads:[~2002-06-25 9:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-14 17:42 ip_conntrack_ftp doesn't work Giovanni Cardone
2002-06-24 19:16 ` Adam Young
2002-06-24 19:30 ` Antony Stone
2002-06-25 9:23 ` Giovanni Cardone
2002-06-25 8:52 ` Jozsef Kadlecsik
2002-06-25 9:27 ` Chris [this message]
2002-06-25 11:42 ` Allowing limited broadcasts between LAN <-> DMZ? Antony Stone
2002-06-25 9:31 ` ip_conntrack_ftp doesn't work Giovanni Cardone
2002-06-25 10:03 ` Jozsef Kadlecsik
2002-06-26 0:17 ` Giovanni Cardone
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=3D18379C.B101AA83@aon.at \
--to=mlists@aon.at \
--cc=netfilter@lists.samba.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.