From: michael@floog.net
To: Aleksandar Milivojevic <amilivojevic@pbl.ca>
Cc: netfilter@lists.netfilter.org
Subject: Re: How to drop/reject packets amongst LAN clients?
Date: Mon, 10 May 2004 11:26:17 -0700 [thread overview]
Message-ID: <1084213577.409fc949e1db4@webmail.floog.net> (raw)
In-Reply-To: <409FB903.1090005@pbl.ca>
Aleksandar,
Thanks for your guidance.
It looks like I've got a fair amount of new reading to do after
receiving Antony, Cedric, and your suggestion. I think I'll want to
install the 3rd NIC, and do some more NAT'ing and/or Bridge'ing.
First stop, www.tldp.org for review of documentation there.
Second stop, man route and/or routed.
I appreciate your help.
Mike
Quoting Aleksandar Milivojevic <amilivojevic@pbl.ca>:
> Second solution would be to put new server onto separate LAN.
> 192.168.1.9 will become 192.168.2.9 (or whatever). Than clients on
> your
> first LAN (192.168.1.0/24) will have to talk to your firewall/router
> to
> get to the server on your second LAN (192.168.2.0/24).
>
> You will need one more ethernet card for second solution. If
> additional
> server is going to be the only host in second LAN, you can connect it
>
> directly with cross over cable. If you are going to add more servers
> to
> second LAN, you will also need additional hub or switch (do not
> connect
> two LANs into same hub).
>
> --
> Aleksandar Milivojevic <amilivojevic@pbl.ca> Pollard Banknote
prev parent reply other threads:[~2004-05-10 18:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-10 16:23 How to drop/reject packets amongst LAN clients? michael
2004-05-10 16:43 ` Antony Stone
2004-05-10 17:31 ` michael
2004-05-10 17:43 ` Antony Stone
2004-05-10 17:14 ` Cedric Blancher
2004-05-10 17:34 ` Antony Stone
2004-05-10 17:46 ` Cedric Blancher
2004-05-10 17:16 ` Aleksandar Milivojevic
2004-05-10 18:26 ` michael [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=1084213577.409fc949e1db4@webmail.floog.net \
--to=michael@floog.net \
--cc=amilivojevic@pbl.ca \
--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.