From: "John Black" <black@arbbs.net>
To: netfilter@lists.netfilter.org
Subject: Re: Destination Nat
Date: Wed, 2 Jun 2004 06:53:12 -0500 [thread overview]
Message-ID: <016f01c44898$2fa221c0$9322a141@black> (raw)
In-Reply-To: 1086175160.4146.1.camel@localhost
okay,
thank you
> -p 6 is the same as -p tcp only a little faster as it does not have to
> look up tcp in the protocols file and translate it from tcp to 6. UDP
> would be -p 17, ICMP -p 1, ESP -p 50, etc.
>
next prev parent reply other threads:[~2004-06-02 11:53 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-28 14:18 Destination Nat black
2004-05-29 1:56 ` John A. Sullivan III
2004-06-02 3:38 ` John Black
2004-06-02 11:19 ` John A. Sullivan III
2004-06-02 11:53 ` John Black [this message]
2004-06-02 15:13 ` Alistair Tonner
-- strict thread matches above, loose matches on Subject: below --
2004-06-04 16:14 black
2004-06-04 16:44 ` John A. Sullivan III
2004-06-04 15:45 black
2004-06-04 16:14 ` John A. Sullivan III
2004-06-02 15:20 Piszcz, Justin Michael
2004-05-28 13:46 black
2004-05-28 14:18 ` John A. Sullivan III
2004-01-28 20:45 Destination NAT Ale Zeta
2004-01-28 14:21 Alejandro Zaidel
2004-01-29 9:13 ` Antony Stone
2004-01-29 9:47 ` Ray Leach
2004-01-29 9:46 ` Antony Stone
2003-03-14 11:01 Sathi
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='016f01c44898$2fa221c0$9322a141@black' \
--to=black@arbbs.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