From: Shawn <core@enodev.com>
To: "Aldo S. Lagana" <alagana@discmail.com>
Cc: 'Netfilter Mailing List' <netfilter@lists.netfilter.org>
Subject: RE: Routing Public IPs over NAT Address Space
Date: 14 Jul 2003 15:49:43 -0500 [thread overview]
Message-ID: <1058215783.24180.128.camel@localhost> (raw)
In-Reply-To: <200307142037.h6EKbDjk022585@discmail.com>
1. I'm not the asker. Are you responding to my response?
2. Soap box: 90% of documentation fails to live up to it's purpose. With
such an overwhelming topic, it can be difficult to get over the first
learning hump. Some folks are willing at least to try and help, even if
only to give pointers to documentation, and it's counter productive to
rag on those people.
On Mon, 2003-07-14 at 15:35, Aldo S. Lagana wrote:
> Read the Tutorial - anyone who configures a firewall and doesn't know the
> firewalling technology that he/she is implementing is asking for problems,
> to say the least.
>
> Google iptables tutorial and spend some time understanding it.
>
> Soap box: 90% of the questions posed to this group are answered in the
> tutorial. It would make this list much less chatty to hear a lot less
> questions about people's 'unique' setups...
next prev parent reply other threads:[~2003-07-14 20:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-14 17:52 Routing Public IPs over NAT Address Space Aaron Clausen
2003-07-14 18:10 ` Shawn
2003-07-14 19:57 ` Rowan Reid
2003-07-14 20:23 ` Shawn
2003-07-14 20:35 ` Aldo S. Lagana
2003-07-14 20:49 ` Shawn [this message]
2003-07-14 22:10 ` A. Clausen
2003-07-14 22:38 ` Shawn
-- strict thread matches above, loose matches on Subject: below --
2003-07-15 0:23 Daniel Chemko
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=1058215783.24180.128.camel@localhost \
--to=core@enodev.com \
--cc=alagana@discmail.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.