From: Wakko Warner <wakko@animx.eu.org>
To: Gnarlodious <lists.gnarlodious@gmail.com>
Cc: netfilter@lists.netfilter.org
Subject: Re: Block LAN DHCP broadcast
Date: Mon, 16 Jul 2007 20:43:55 -0400 [thread overview]
Message-ID: <20070717004355.GA13667@animx.eu.org> (raw)
In-Reply-To: <3130eec50707161010q62a32011p527c11ca9026f07f@mail.gmail.com>
Please keep list mail on the list.
Gnarlodious wrote:
> On 7/16/07, Wakko Warner wrote:
> >Gnarlodious wrote:
> >> I would need to have another
> >> device on the UPS battery. I want to have only two devices taking
> >> power from the UPS battery, the modem and the server.
> >
> >A diagram might be more helpful.
> http://etc.Gnarlodious.com/Images/Lan1.png
So you have a dsl connection with 3 computers and a wireless router
connected directly to it. I would assume that you want to keep those 3
computers from getting an IP via DHCP from the dsl modem? From the
networking perspective, unless the ups is actually networked, has nothing to
do with the network. (Personally, I would assign a static IP to the UPS).
Does the DSL modem have a built in hub?
From the AP1 you have 2 PCs and another wireless router. Are these getting
their IP from AP1?
From AP2 you have 2 PCs and nothing else. Since I don't know the interfaces
on the AP devices, I don't know if they are routing traffic or switching
traffic.
I guess the real question is, does the 4 devices connected (according to
your diagram) directly to your DSL modem have non-private IPs?
(private IP ranges: http://tools.ietf.org/html/rfc1918 section 3).
> >DHCP is broadcast when one requests an IP. That's why it's D(ynamic)HCP.
> OK, I'm starting to understand that what I want can't be done.
>
> >The best way I can think of is to have a system (computer, router, whatever
> >running linux) with 2 bridged interfaces and block DHCP traffic going
> >across
> >the bridge.
> Any page that explains how to set that up? I'm not a network pro...
The man page for ebtables and brctl. You'll need a linux kernel with
bridging (802.1d support), ebtables enabled (Personaly, I just enable all
the netfilter modules and let the system decide at runtime which onces to
load), the drivers for 2 nics (I used 3c905b cards on a celeron 600 pc,
throughput is around 8-9mb/sec).
> And thanks for the hint about ebtables.
You could probably do it with iptables on a bridging interface, but ebtables
might be easier.
--
Lab tests show that use of micro$oft causes cancer in lab animals
Got Gas???
next prev parent reply other threads:[~2007-07-17 0:43 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
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 [this message]
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=20070717004355.GA13667@animx.eu.org \
--to=wakko@animx.eu.org \
--cc=lists.gnarlodious@gmail.com \
--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