From: zynkx <skydive@megamail.pt>
To: netfilter@lists.netfilter.org
Subject: dhcrelay
Date: Fri, 28 Nov 2003 20:30:16 +0000 [thread overview]
Message-ID: <1070051416.3fc7b058800c7@paris-hme1> (raw)
_______________
| gateway 1 |
|192.168.0.253|
|81.84.40.XX |
_______________
_______________|
| |
_______________ |
|DHCP SERVER | |
|192.168.0.1 | |
|_____________| |
|
________________
|GATEWAY2 |
|192.168.0.253 |
|192.168.100.254
|______________|
|
|
_________________________________
| |
|
_______________ _______________
______________
|192.168.100.1 | |192.168.100.2|
|192.168.100.3| _______________ ______________
_______________
hi all:
i have this lan i am supposed to use dhcrelay on
gateway 2 so the 192.168.100.0/24 machines can get an
ip address. 192.168.0.1 is the dhcp serveer.i have the
input and output chain of the
gateway 2 to drop.
my question is:
do those request require input and output to accept? i
don't really think so because those packer are not for
gateway 2 but are to be routed to 192.168.100.0/24
machines...
what do you guys think of this??
sorry for the very bad drawing...
tanx ;))))
unix is user friendly. it's just selective when
choosing
friends.
-------------------------------------------------
Email Enviado utilizando o serviço MegaMail
----- Final da mensagem re-enviada -----
unix is user friendly. it's just selective when
choosing
friends.
-------------------------------------------------
Email Enviado utilizando o serviço MegaMail
next reply other threads:[~2003-11-28 20:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-28 20:30 zynkx [this message]
2003-11-28 21:01 ` dhcrelay Jeffrey Laramie
2003-11-29 2:34 ` dhcrelay Ramin Dousti
-- strict thread matches above, loose matches on Subject: below --
2003-11-29 0:56 dhcrelay zynkx
2003-11-29 1:39 ` dhcrelay Jeffrey Laramie
2003-11-29 8:33 ` dhcrelay Ralf Spenneberg
2005-02-15 20:58 dhcrelay Dr. Lars Hanke
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=1070051416.3fc7b058800c7@paris-hme1 \
--to=skydive@megamail.pt \
--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