From: "Alexis" <alexis@attla.net.ar>
To: netfilter@lists.netfilter.org
Subject: Re: How to setup netfilter to stop outbound DHCP?
Date: Sun, 29 Feb 2004 18:11:07 -0300 [thread overview]
Message-ID: <002001c3ff08$8c27ddb0$51a2fea9@heretic> (raw)
In-Reply-To: 001001c3fefd$daf70a70$6401a8c0@LSchmitt
A router is a solution.
----- Original Message -----
From: "Dr. Lawrence J. Schmitt" <lschmitt@cbu.edu>
To: <netfilter@lists.netfilter.org>
Sent: Sunday, February 29, 2004 4:54 PM
Subject: How to setup netfilter to stop outbound DHCP?
>
> I am setting up a lab for students to configure and experiment with
> Linux. I need to set up something that will keep responses to DHCP
> requests from leaving the lab to keep from driving the network support
> people crazy.
> 1. What is the appropriate tool to use?
> 2. Can anyone suggest an iptables rule that will block either
> dhcp requests from entering the lab subnet or responses from
> exiting.
> 3. I would like to set up one pc running Linux as a router and
> firewall, filter that also would run DHCP and DNS for the local
> lab as well as block responses to DHCP requests on the nic that
> is connected to the campus network.
>
> Any thoughts or comments are appreciated.
>
> Thanks in advance,
>
> Larry Schmitt
>
>
>
>
>
>
prev parent reply other threads:[~2004-02-29 21:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040229143928.7884.68000.Mailman@netfilter-sponsored-by.noris.net>
2004-02-29 15:44 ` Re: Filtering using port+process (i.e. open port 80 for Apache only) Moath A. Khalaf
2004-02-29 15:57 ` Zone alarm [was: Re: Re: Filtering using port+process (i.e. open port 80 for Apache only)] Antony Stone
2004-02-29 19:54 ` How to setup netfilter to stop outbound DHCP? Dr. Lawrence J. Schmitt
2004-02-29 20:07 ` Antony Stone
2004-02-29 20:22 ` Jeroen Vriesman
2004-02-29 21:11 ` Alexis [this message]
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='002001c3ff08$8c27ddb0$51a2fea9@heretic' \
--to=alexis@attla.net.ar \
--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;
as well as URLs for NNTP newsgroup(s).