From: "Chris K Ellsworth" <cke@highlandshighspeed.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] How to make Linux server transparent to internal machines?
Date: Fri, 31 May 2002 22:01:52 +0000 [thread overview]
Message-ID: <marc-lartc-102288255200576@msgid-missing> (raw)
In-Reply-To: <marc-lartc-102288207332583@msgid-missing>
what you want to do is setup a bridgeing firewall
http://bridge.sourceforge.net/
----- Original Message -----
From: "Neil Aggarwal" <neil@JAMMConsulting.com>
To: <lartc@mailman.ds9a.nl>
Sent: Friday, May 31, 2002 2:55 PM
Subject: [LARTC] How to make Linux server transparent to internal machines?
> Hello:
>
> I have a block of static IP addresses on which I want to run
> several Windows machines.
>
> Since I want to have a firewall, I was thinking of using 1 IP
> address for a linux server that will act as a firewall for
> the entire setup.
>
> So, here is a diagram:
>
> [Internet] -- [Linux Server] -- switch -- [Internal machines]
>
> The linux server and the internal machines all have static
> IP addresses which are public to the Internet.
>
> How can I set-up routing so the Linux server is "transparent"
> to the other machines?
>
> Thanks,
> Neil.
>
> --
> Neil Aggarwal
> JAMM Consulting, Inc. (972) 612-6056, http://www.JAMMConsulting.com
> Custom Internet Development Websites, Ecommerce, Java, databases
>
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
>
>
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2002-05-31 22:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-31 21:55 [LARTC] How to make Linux server transparent to internal machines? Neil Aggarwal
2002-05-31 22:01 ` Chris K Ellsworth [this message]
2002-06-01 7:41 ` Stef Coene
2002-06-01 13:33 ` JoseCarlos.Ramirez
2002-06-03 15:41 ` Michael T. Babcock
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=marc-lartc-102288255200576@msgid-missing \
--to=cke@highlandshighspeed.net \
--cc=lartc@vger.kernel.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.