From: "John A. Sullivan III" <john.sullivan@nexusmgmt.com>
To: alucard@kanux.com
Cc: netfilter@lists.netfilter.org
Subject: Re: forwarding
Date: Tue, 18 May 2004 10:51:17 -0400 [thread overview]
Message-ID: <1084891877.6418.28.camel@localhost> (raw)
In-Reply-To: <34002.200.44.170.105.1084891760.squirrel@200.44.170.105>
On Tue, 2004-05-18 at 10:49, alucard@kanux.com wrote:
> > [JAS - isn't the packet coming in on 10.73.219.156? In other words, your
> > NAT rule should be:
> > iptables -t nat -A PREREOUTING -d 10.73.219.156 -p 6 --dport 8080 -j
> > DNAT --to-destination 192.168.0.2:80]
>
> -p 6? I've never seen this before, what is that rule trying to do?
>
<snip>
Ah, I usually use the protocol numbers directly rather than the names of
the protocols as it saves the lookup to the /etc/protocols file. 6 is
the IP protocol number for TCP. It is the same as saying -p tcp but a
little faster. The main point was the destination address appears to be
wrong - John
--
John A. Sullivan III
Chief Technology Officer
Nexus Management
+1 207-985-7880
john.sullivan@nexusmgmt.com
next prev parent reply other threads:[~2004-05-18 14:51 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-18 14:22 forwarding alucard
2004-05-18 14:39 ` forwarding John A. Sullivan III
2004-05-18 14:49 ` forwarding alucard
2004-05-18 14:51 ` John A. Sullivan III [this message]
2004-05-18 14:56 ` forwarding Antony Stone
2004-05-18 14:57 ` forwarding alucard
2004-05-18 14:58 ` forwarding John A. Sullivan III
2004-05-18 15:12 ` forwarding alucard
2004-05-18 15:53 ` forwarding John A. Sullivan III
2004-05-18 16:38 ` forwarding alucard
2004-05-18 17:02 ` forwarding John A. Sullivan III
2004-05-18 18:21 ` forwarding alucard
2004-05-18 18:28 ` forwarding Antony Stone
2004-05-18 18:42 ` forwarding alucard
2004-05-18 19:22 ` forwarding John A. Sullivan III
2004-05-18 21:33 ` forwarding Antony Stone
2004-05-19 4:56 ` forwarding Juan Hernandez
2004-05-18 15:09 ` forwarding Antony Stone
2004-05-18 15:40 ` forwarding alucard
2004-05-18 15:53 ` forwarding Antony Stone
2004-05-18 14:44 ` forwarding Antony Stone
-- strict thread matches above, loose matches on Subject: below --
2005-03-26 17:48 forwarding amir_sarbazi
2004-05-18 20:48 forwarding Daniel Chemko
2004-05-18 21:15 ` forwarding John A. Sullivan III
2004-05-18 20:33 forwarding Daniel Chemko
2004-05-18 18:23 forwarding Daniel Chemko
2004-05-18 18:42 ` forwarding Antony Stone
2004-05-18 18:50 ` forwarding alucard
2004-05-18 19:15 ` forwarding John A. Sullivan III
2004-05-18 18:04 forwarding Daniel Chemko
2004-05-18 17:04 forwarding CPD - David Cardeñosa Rubio
2004-05-18 15:33 forwarding CPD - David Cardeñosa Rubio
2004-05-18 15:47 ` forwarding John A. Sullivan III
2004-05-18 15:51 ` forwarding Antony Stone
2002-07-08 3:25 forwarding Tim
2002-07-08 0:30 ` forwarding Antony Stone
[not found] ` <003801c22632$521c93a0$1606d6d1@nebuchadnezza>
2002-07-08 0:53 ` forwarding Antony Stone
2002-07-08 4:03 ` forwarding Tim
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=1084891877.6418.28.camel@localhost \
--to=john.sullivan@nexusmgmt.com \
--cc=alucard@kanux.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.