From: Christopher Nielsen <cnielsen@pobox.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] IL and NAT
Date: Fri, 17 Nov 2000 16:50:25 -0800 [thread overview]
Message-ID: <Pine.BSF.4.21.0011171638320.44546-100000@cassandra.foobarbaz.net> (raw)
In-Reply-To: <20001118001754.DE2F0199E1@mail.cse.psu.edu>
On Fri, 17 Nov 2000 geoff@x.bell-labs.com wrote:
> NAT routers generally have to rewrite port numbers (not
> just IP addresses) for protocols that use them, and
> ports numbers are at different offsets and of
> potentially different sizes in different protocol's
> headers. IL's port numbers appear later than TCP's and
> UDP's, for example. NAT routers will generally
> understand the headers of TCP, UDP and ICMP at minimum,
> but I haven't encountered one yet that understood IL
> (even Lucent's own).
That makes perfect sense, and if I would have been a little
more patient and thought it through, I probably would have
figured that out.
That said, I have some sway with Cisco's development team,
so I _might_ be able to get them to implement support for
IL. I'll let you know how it goes.
--
Christopher Nielsen
cnielsen@pobox.com
next prev parent reply other threads:[~2000-11-18 0:50 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 [this message]
2000-11-18 1:19 ` Boyd Roberts
2000-11-18 3:02 ` Scott Schwartz
-- 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=Pine.BSF.4.21.0011171638320.44546-100000@cassandra.foobarbaz.net \
--to=cnielsen@pobox.com \
--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).