9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Boyd Roberts" <boyd@planete.net>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] IL and NAT
Date: Sat, 18 Nov 2000 02:19:31 +0100	[thread overview]
Message-ID: <004701c050fd$a481eca0$0ab9c6d4@cybercable.fr> (raw)
In-Reply-To: <20001118001754.DE2F0199E1@mail.cse.psu.edu>

From: <geoff@x.bell-labs.com>

> NAT routers generally have to rewrite port numbers (not just IP
> addresses) ...

yes, i tracked down a particularly nasty case of a firewall
doing NAT to UDP packets with a destination port of 53 [DNS].
i found that some DNS servers would not reply to requests
that didn't have a source port of 53; NAT having munged
the source address and port.

i would have found it a lot faster if my pleas for a
protocol analyser had been heeded -- i'd only been
bitching about it for a _year_.  somehow i managed
to forge up some queries that demonstrated the
problem.

i also had the added stumbling block of not knowing or
being able to know the firewall's config.  contractors
were prohibited from going near them, except when things
were _really_ screwed up.

``oh, but that's impossible, boyd... err, i see''.




  parent reply	other threads:[~2000-11-18  1:19 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 [this message]
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='004701c050fd$a481eca0$0ab9c6d4@cybercable.fr' \
    --to=boyd@planete.net \
    --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).