9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: lucio@proxima.alt.za
To: 9fans@9fans.net
Subject: Re: [9fans] tcp port scanner
Date: Fri, 12 Dec 2014 05:50:43 +0200	[thread overview]
Message-ID: <fcee803bdd470fcf5d650b1effd581b9@proxima.alt.za> (raw)
In-Reply-To: <e24a1406bc3ba7bc4b37979dd66e2286@sigma.offblast.org>

> it turns out the right thing to do is to just consult cs directly,
> which can resolve any of 1.2.3.4, google.com, finn (where ndb has a
> sys=finn line), '$ipgw'.

Ndb's only incurable problem (it may be curable, but it looks hard) is
that it is strictly case sensitive in places, like the ethernet
address, where it would be preferable if it wasn't.

I have yet to find a practical reason to disconnect domain names and
IP addresses, but that could be another stumbling block.

For the rest, I think the design is pretty sound, even remarkable.

Lucio.




      reply	other threads:[~2014-12-12  3:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-11  6:56 mischief
2014-12-11  7:53 ` mischief
2014-12-12  3:14   ` mischief
2014-12-12  3:50     ` lucio [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=fcee803bdd470fcf5d650b1effd581b9@proxima.alt.za \
    --to=lucio@proxima.alt.za \
    --cc=9fans@9fans.net \
    /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).