All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Jacob <jacob@internet24.de>
To: netfilter@lists.netfilter.org
Subject: Re: Block LAN DHCP broadcast
Date: Mon, 16 Jul 2007 17:30:05 +0200	[thread overview]
Message-ID: <1184599806.17688.105.camel@localhost> (raw)
In-Reply-To: <3130eec50707160738o418b7a9m43f68af0c6a9afe4@mail.gmail.com>

On Mon, 2007-07-16 at 08:38 -0600, Gnarlodious wrote:
> Thanks for the quick response. Not sure I understand all of that...
> Yes, this LAN is all on one IP range. The routers are all connected
> with ethernet.
> 
> I don't want to block client computers, but I understand that if I
> drop DHCP ports 67 and 68 to and from other routers then DHCP will be
> handled by the router the computer is connected to. Is that right?

AFAIK, DHCP request aren't usually passed on by (Linux) routers
(Pseudo-UDP/IP-Packet to 255.255.255.255/FF:FF:FF:FF:FF:FF Port), and if
they were, you could probably simply stop them  by filtering everything
to udp
destination port 68. What makes you think that your router passes
on DHCP requests?

On the contrary, one usually does have to put in
a bit of effort to allow dhcp over routers (=> dhcp relay)...





  reply	other threads:[~2007-07-16 15:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-16 13:52 Block LAN DHCP broadcast Gnarlodious
2007-07-16 14:17 ` Thomas Jacob
2007-07-16 14:38   ` Gnarlodious
2007-07-16 15:30     ` Thomas Jacob [this message]
2007-07-16 16:07       ` Gnarlodious
2007-07-16 16:37         ` Wakko Warner
     [not found]           ` <3130eec50707161010q62a32011p527c11ca9026f07f@mail.gmail.com>
2007-07-17  0:43             ` Wakko Warner
2007-07-17  1:40               ` Gnarlodious
2007-07-17 16:26                 ` Wakko Warner
     [not found]       ` <1385.192.168.0.216.1184602063.squirrel@192.168.0.216>
2007-07-16 17:07         ` Thomas Jacob
2007-07-16 18:09 ` Gregory Carter

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=1184599806.17688.105.camel@localhost \
    --to=jacob@internet24.de \
    --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 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.