From: edwardspl@ita.org.mo
To: "John A. Sullivan III" <jsullivan@opensourcedevelopmentcorp.com>
Cc: Netfilter users list <netfilter@lists.netfilter.org>
Subject: Re: NAT + Firewall
Date: Sun, 02 Jan 2005 15:14:42 +0800 [thread overview]
Message-ID: <41D79F62.CEC8717C@ita.org.mo> (raw)
In-Reply-To: 1104645369.8653.2.camel@jasiiitosh.opensourcedevel.com
Dear John,
Is there some of samples for user to study ?
Thanks!
Edward.
"John A. Sullivan III" wrote:
> On Sat, 2005-01-01 at 14:39 +0800, edwardspl@ita.org.mo wrote:
> > Dear All,
> >
> > Happy New Year !
> >
> > I want to know how to set the nat and firewall, then all of the client
> > PCs needn't to via ( throught ) leased line / broadband again, means
> > direct to internal network to connect with Internet Server ?
> >
> > Many thank for your help !
> >
> > Edward.
> >
> >
> >
> I would suggest that you read Oskar Andreasson's excellent tutorial on
> using iptables. You can find it in the tutorials section of the
> netfilter web page (http://www.netfilter.org). There are also some
> slide shows available in the training section at
> http://iscs.sourceforge.net
> You could also use a GUI configuration like fwbuilder
> (http://www.fwbuilder.org) to make this easier. When ISCS is ready, it
> will automatically configure even the most complex NAT such as nested,
> overlapping and range NAT. Good luck in your studies - John
> --
> John A. Sullivan III
> Open Source Development Corporation
> +1 207-985-7880
> jsullivan@opensourcedevel.com
>
> Financially sustainable open source development
> http://www.opensourcedevel.com
next prev parent reply other threads:[~2005-01-02 7:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-01 6:39 NAT + Firewall edwardspl
2005-01-02 5:56 ` John A. Sullivan III
2005-01-02 7:14 ` edwardspl [this message]
2005-01-02 13:09 ` John A. Sullivan III
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=41D79F62.CEC8717C@ita.org.mo \
--to=edwardspl@ita.org.mo \
--cc=jsullivan@opensourcedevelopmentcorp.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 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.