From: Jason Opperisano <opie@817west.com>
To: netfilter@lists.netfilter.org
Subject: Re: NAT problem when coming from private network
Date: Fri, 22 Apr 2005 00:22:55 -0400 [thread overview]
Message-ID: <20050422042255.GA2412@bender.817west.com> (raw)
In-Reply-To: <6.0.1.1.2.20050421193231.01d01a20@insight.ip3.com>
On Thu, Apr 21, 2005 at 07:35:33PM -0700, Royce Kemp wrote:
> at first this is what I thought the solution would be, but Mark Wells said
> that his mail server is on the same subnet as the client machine
> (192.168.1.8 and 192.168.1.34)... so why can't the mail server communicate
> directly with the client machine? so packet go from client to firewall and
> are redirected to the mail server.. then the mail server will arp for
> 192.168.1.34 and return packet directly to him). is this not possible?
just as people refuse to search the ML archives, i refuse to re-type
this email for the 50th time. speaking of #50--here it is:
http://marc.theaimsgroup.com/?l=netfilter&m=110571844432115&w=2
-j
--
"Stewie: OK, Harold, what do you think of our Mad Lib
Stewie: "Cinderella had two step-'watermelons', who were very 'smelly'
to her. So her fair god'toilet' turned her pumpkin into a big 'fanny',
and dragged her off to the 'poop'.
Stewie: Oh, how ruthlessly absurd."
--Family Guy
next prev parent reply other threads:[~2005-04-22 4:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-21 20:24 NAT problem when coming from private network Mark Wells
2005-04-22 2:16 ` Alistair Tonner
2005-04-22 2:35 ` Royce Kemp
2005-04-22 3:39 ` Taylor Grant
2005-04-22 4:22 ` Jason Opperisano [this message]
2005-04-22 4:03 ` Taylor Grant
2005-04-27 20:59 ` Mark Wells
2005-04-27 21:03 ` Mark Wells
-- strict thread matches above, loose matches on Subject: below --
2005-04-22 2:42 Gary W. Smith
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=20050422042255.GA2412@bender.817west.com \
--to=opie@817west.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.