Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Jim Laurino <nfcan.x.jimlaur@dfgh.net>
To: netfilter@lists.netfilter.org
Subject: Re: dhcrelay still responds dropped inbound offer packets from iptables (nfcan: addressed to exclusive sender for this address)
Date: Fri, 8 Jul 2005 17:37:49 -0400	[thread overview]
Message-ID: <20050708213749.GC17745@salty> (raw)
In-Reply-To: <673fb82305070814186036ce2f@mail.gmail.com> (from +nfcan+jimlaur+7a8d75f853.changwilly#gmail.com@spamgourmet.com on Fri, Jul 08, 2005 at 17:18:33 -0400)

On 2005.07.08 17:18, Willy Chang - changwilly@gmail.com wrote:
> Folks,
> 
>      I am running a dhrelay service and using iptables to be a
> firewall to block packets from dhcp server on the inbound side, eth0,
> of my Liunx. The reason to do this is to avoid generating duplicated
> packets from my machine to dhcp client on the same subnet.
>      For some reasons, I am unable to block these packets. I have a
> simple rule setting below to simply block all incoming UDP packets
> where it should block dhcp package as well.
> 
> iptables -A INPUT -p UDP -i eth0 -j DROP

I see two things to comment on.

First, if you add (-A) a rule like this at the end,
the packets in question might have already been accepted
by an earlier rule. For a case like this, you might want
to insert at the top (-I) instead.

Second, INPUT affects filtering of packets bound for the firewall
host itself. FORWARD rules affect packets bound for other hosts.
I think those are the packets you are trying to block.

-- 
Jim Laurino
nfcan.x.jimlaur@dfgh.net
Please reply to the list.
Only mail from the listserver reaches this address.


  reply	other threads:[~2005-07-08 21:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-08 21:18 dhcrelay still responds dropped inbound offer packets from iptables Willy Chang
2005-07-08 21:37 ` Jim Laurino [this message]
2005-07-11  7:32 ` Harald Welte
2005-07-11 11:14   ` Jan Engelhardt

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=20050708213749.GC17745@salty \
    --to=nfcan.x.jimlaur@dfgh.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