From: gerardo arnaez <garnaez@gmail.com>
To: Jason Opperisano <opie@817west.com>, netfilter@lists.netfilter.org
Subject: Re: http connection hangs when connecting to forwarded IP
Date: Sat, 14 May 2005 15:30:25 -0700 [thread overview]
Message-ID: <148eea7105051415307d1907d1@mail.gmail.com> (raw)
In-Reply-To: <20050514220123.GA25471@bender.817west.com>
Duh!
*smacks forward*
On 5/14/05, Jason Opperisano <opie@817west.com> wrote:
> On Sat, May 14, 2005 at 02:52:44PM -0700, gerardo arnaez wrote:
> > aah so while I was forawrdin all from internal nic to external, I was
> > fowarding anything omfr extermal to inernter,
> >
> > but I thought NAT did the forwarding as part of being NAt
>
> NAT rewrites source and destination IP addresses (and ports) in packet
> headers, that is all.
>
> -j
>
> --
> "Narrator: Remember, nothing says "good job" like a firm, open-palm
> slap on the behind."
> --Family Guy
>
>
prev parent reply other threads:[~2005-05-14 22:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-13 17:27 http connection hangs when connecting to forwarded IP gerardo arnaez
2005-05-14 6:59 ` Jason Opperisano
2005-05-14 21:52 ` gerardo arnaez
2005-05-14 22:01 ` Jason Opperisano
2005-05-14 22:30 ` gerardo arnaez [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=148eea7105051415307d1907d1@mail.gmail.com \
--to=garnaez@gmail.com \
--cc=netfilter@lists.netfilter.org \
--cc=opie@817west.com \
/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