From: gypsy <gypsy@iswest.com>
To: lartc@vger.kernel.org
Subject: [LARTC] Do I need NAT?
Date: Fri, 11 Mar 2005 07:50:29 +0000 [thread overview]
Message-ID: <42314DC5.CC0F8AB4@iswest.com> (raw)
In-Reply-To: <42314B5A.C24E0E0@iswest.com>
OOPS!
I said "When a packet is received from ISP1, is a NAT rule
necessary for that packet to get to the NNTP computer?"
What I meant is ISP2, not ISP1.
--
gypsy
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
prev parent reply other threads:[~2005-03-11 7:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-11 7:40 [LARTC] Do I need NAT? gypsy
2005-03-11 7:50 ` gypsy [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=42314DC5.CC0F8AB4@iswest.com \
--to=gypsy@iswest.com \
--cc=lartc@vger.kernel.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