9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Lyndon Nerenberg <lyndon@orthanc.ca>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] bug in authdial()
Date: Sat, 21 May 2016 16:11:30 -0700	[thread overview]
Message-ID: <E362EE3C-5B18-4D34-B964-54E768EC27BD@orthanc.ca> (raw)
In-Reply-To: <ee8d9c4e298eb81f8ea27ce180754902@lilly.quanstro.net>


> On May 21, 2016, at 10:04 AM, erik quanstrom <quanstro@quanstro.net> wrote:
> 
> this problem is a little easier to fix.  cs needs to do a little more work to filter out
> impossible connection types.  for example, if one's internet connection is not ip6
> capable, then cs should be instructed to not return ip6 addresses.

Yes, exactly.  And doesn't/didn't ndb have a tag that was used to indicate whether a system or network used il?  (proto=il? I don't have access to a 9labs machine to check at the moment.)

Determining ip6 connectivity shouldn't be that hard.  If you have a route, you connect.  If you don't, the network stack does a fast ENOROUTE return and the case falls through to the next address family.

IL is a bit trickier, since you can't know in advance if the destination supports it, thus the ndb tags I'm vaguely remembering.  And if my memory is correct, the fix for that would be to default 'supports IL' to no, if that's not already the case.


  reply	other threads:[~2016-05-21 23:11 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-18  0:43 arisawa
2016-05-18  9:14 ` cinap_lenrek
2016-05-19 14:45   ` arisawa
2016-05-19 15:43     ` lucio
2016-05-19 15:48       ` Charles Forsyth
2016-05-20  4:58         ` arisawa
2016-05-20 22:04         ` Skip Tavakkolian
2016-05-20 22:25           ` Charles Forsyth
2016-05-21  4:46             ` arisawa
2016-05-21 17:04               ` erik quanstrom
2016-05-21 23:11                 ` Lyndon Nerenberg [this message]
2016-05-21 23:16                   ` erik quanstrom
2016-05-21 17:06             ` erik quanstrom
2016-05-21  3:24           ` arisawa
2016-05-23 14:27           ` arisawa
2016-05-20 22:07         ` Skip Tavakkolian
2016-05-21  2:25           ` Skip Tavakkolian
2016-05-21  7:00             ` arisawa
2016-05-21 16:51               ` erik quanstrom
2016-05-21 21:45                 ` Skip Tavakkolian
2016-05-21 21:48                   ` erik quanstrom
2016-05-21 22:16                     ` Skip Tavakkolian
2016-05-21 21:50                   ` erik quanstrom
2016-05-21 22:17                     ` Skip Tavakkolian
2016-05-21 22:34                       ` erik quanstrom
2016-05-21 23:03                         ` Skip Tavakkolian
2016-05-21 23:31                           ` erik quanstrom
2016-05-21 22:53                     ` David du Colombier
2016-05-18 13:06 ` Charles Forsyth
2016-05-18 17:03   ` Skip Tavakkolian
2016-05-19  4:07     ` arisawa

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=E362EE3C-5B18-4D34-B964-54E768EC27BD@orthanc.ca \
    --to=lyndon@orthanc.ca \
    --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).