From: Jeremy Jackson <jerj@coplanar.net>
To: netfilter@lists.netfilter.org
Subject: broadcast packets DROPped, still received by dhcrelay
Date: Tue, 17 Feb 2004 16:22:31 -0500 [thread overview]
Message-ID: <40328617.3070104@coplanar.net> (raw)
Hi,
(Please CC - I'm not subscribed)
I've searched the list archives, regarding broadcasts, DHCP, and raw
sockets. I still can't explain the following behaviour.
A Linux router running dhcrelay 3.x is configured to DROP incoming dhcp
requests from an interface that are from 0.0.0.0/32 and to
255.255.255.255. The rule in the mange PREROUTING table matches, and a
later rule in the mangle INPUT rule confirms that the dropped packet
stops being processed. (1st conter increases, 2nd doesn't increase)
However, the dhcrelay process still appears to receive the packet.
netstat -anp doesn't show any raw type sockets
udp 0 0 0.0.0.0:67 0.0.0.0:* 14127/dhcrelay3
as can be seen on a similar machine running dhcpd:
udp 0 0 0.0.0.0:67 0.0.0.0:* 19850/dhcpd3
raw 0 0 0.0.0.0:1 0.0.0.0:* 7 19850/dhcpd3
how can the lone udp socket bypass netfilter like this? Is there any
way to filter this with iptables?
Thanks,
Jeremy Jackson
reply other threads:[~2004-02-17 21:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=40328617.3070104@coplanar.net \
--to=jerj@coplanar.net \
--cc=netfilter@lists.netfilter.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