From: "Mark E. Donaldson" <markee@bandwidthco.com>
To: 'Jim Cliver' <jclive@mtaonline.net>, netfilter@lists.netfilter.org
Subject: RE: IPTables Flow Chart
Date: Thu, 11 Mar 2004 20:00:59 -0800 [thread overview]
Message-ID: <200403120400.i2C40rfG014733@server5.bandwidthco.com> (raw)
In-Reply-To: <4050C869.8080506@mtaonline.net>
Nice job Jim. You've packed a considerable amount of complex stuff into a
very small space. I'm sure many will find this beneficial.
-----Original Message-----
From: netfilter-admin@lists.netfilter.org
[mailto:netfilter-admin@lists.netfilter.org] On Behalf Of Jim Cliver
Sent: Thursday, March 11, 2004 12:13 PM
To: netfilter@lists.netfilter.org
Subject: Re: IPTables Flow Chart
Jim Cliver wrote:
>> Thank you to all that replied to my first posting of the drawing, I
>> really appreciate the feedback!
>>
>> I believe that all of your suggestions and comments have been
>> incorporated into this revision...
>>
>> http://www.aptalaska.net/~jclive/IPTablesFlowChart.pdf
>>
>> As always, your comments, suggestions and corrections are welcome.
>>
>> Regards,
>> jim
>>
>>
>>
> Sorry Folks,
>
> Just found an error, will correct and repost. Directonal arrows from
> Interface B to PREROUTING process are missing...
>
> jim
>
>
>
Ok, we should be good to go now! The link above is still good dwg'ng has
been updated.
Thanks also to Antony for the quick catch!
jim
next prev parent reply other threads:[~2004-03-12 4:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-10 2:24 IPTables Flow Chart Jim Cliver
2004-03-10 18:44 ` Very impressive, and no virus :-) " Xinwen Fu
2004-03-10 19:08 ` Antony Stone
2004-03-11 19:25 ` Jim Cliver
2004-03-11 19:41 ` Jim Cliver
2004-03-11 20:13 ` Jim Cliver
2004-03-12 3:33 ` Kiran Kumar
2004-03-12 4:00 ` Mark E. Donaldson [this message]
2004-03-11 19:42 ` Antony Stone
-- strict thread matches above, loose matches on Subject: below --
2004-03-12 4:39 Babar Kazmi
2004-03-12 5:11 ` Kiran Kumar
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=200403120400.i2C40rfG014733@server5.bandwidthco.com \
--to=markee@bandwidthco.com \
--cc=jclive@mtaonline.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox