From: "John A. Sullivan III" <jsullivan@opensourcedevel.com>
To: Jojo Solis <jojo.solis@summitmedia.com.ph>
Cc: netfilter@lists.netfilter.org
Subject: Re: Help creating a RULE
Date: Mon, 19 Sep 2005 06:10:23 -0400 [thread overview]
Message-ID: <1127124623.2656.7.camel@localhost> (raw)
In-Reply-To: <CBF2220F040BC54584E69D569377DC4D41698F@smg-mail.summitmedia.com.ph>
On Mon, 2005-09-19 at 08:39 +0800, Jojo Solis wrote:
> Hi Everyone,
>
>
> We have firewall with 3 LAN Card, Eth0 is connected to my LAN, eth1 is
> Connected to Internet, and eth2 is connected to our Sister companies
> WAN.
>
> Since I am new to IPtables i dont know how to create a Rule to make the
> packet successfully reach its destination. This setup was made by a
> former sysad but left the firewall especially the connection going to
> the Sister Companies WAN un-configured. So that's the reason why Im here
> to seek help creating a rule for this firewall.
>
> Basically I want to achive the following.
>
> 1. Allow any IN and OUT traffic from eth0 to eth2 and vice versa.
> 2. Allow IN and OUT http traffic from eth0 to eth1.
> 3. Allow IN and OUT SMTP traffic from eth0 to eth1.
> 4. Allow Outgoing FTP traffic from eth0 to Eth1, Plus allow ESTABLISHED
> and RELATED FTP connection.
<snip>
For something this basic, you are best off reading a good tutorial.
There is an excellent one by Oskar Andreasson at
http://iptables-tutorial.frozentux.net/iptables-tutorial.html and it
makes for very quick reading. You can also find some slightly dated
training slide shows in the training section of
http://iscs.sourceforge.net - 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
prev parent reply other threads:[~2005-09-19 10:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-19 0:39 Help creating a RULE Jojo Solis
2005-09-19 3:32 ` Edmundo Carmona
2005-09-19 10:10 ` John A. Sullivan III [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=1127124623.2656.7.camel@localhost \
--to=jsullivan@opensourcedevel.com \
--cc=jojo.solis@summitmedia.com.ph \
--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.