From: Scott Schwartz <schwartz@bio.cse.psu.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] IL and NAT
Date: Fri, 17 Nov 2000 22:02:08 -0500 [thread overview]
Message-ID: <20001118030208.7775.qmail@g.bio.cse.psu.edu> (raw)
In-Reply-To: Message from geoff@x.bell-labs.com of "Fri, 17 Nov 2000 19:17:47 EST." <20001118001754.DE2F0199E1@mail.cse.psu.edu>
| Contrary to what Scott just said, it's not each application that has
| to be added to a NAT router, but each protocol that rides directly on
| IP (or beside it).
Isn't it the case that some applications, like ftp, encode ip address
and port information in application layer traffic, which NAT has to
account for? Linux seems to have code to handle that sort of stuff
(linux/net/ipv4/ip_masq*).
next prev parent reply other threads:[~2000-11-18 3:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-18 0:17 geoff
2000-11-18 0:50 ` Christopher Nielsen
2000-11-18 1:19 ` Boyd Roberts
2000-11-18 3:02 ` Scott Schwartz [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-11-18 18:42 nigel
2000-11-18 19:00 ` Theo Honohan
2000-11-18 19:24 ` Boyd Roberts
2000-11-18 14:04 presotto
2000-11-18 6:32 anothy
2000-11-18 3:21 geoff
2000-11-18 13:53 ` Theo Honohan
[not found] <cnielsen@pobox.com>
2000-11-17 23:48 ` Christopher Nielsen
2000-11-17 23:56 ` Scott Schwartz
2000-11-18 14:20 ` Steve Kilbane
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=20001118030208.7775.qmail@g.bio.cse.psu.edu \
--to=schwartz@bio.cse.psu.edu \
--cc=9fans@cse.psu.edu \
/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;
as well as URLs for NNTP newsgroup(s).