From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] bug in authdial()
Date: Sat, 21 May 2016 16:16:34 -0700 [thread overview]
Message-ID: <8b9ac9787ef7d5263ae46a9e016943c9@lilly.quanstro.net> (raw)
In-Reply-To: <E362EE3C-5B18-4D34-B964-54E768EC27BD@orthanc.ca>
> 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.
cs uses hard-coded rules. one could argue that it's up to dns to filter out
ip6, which would be straightforward one would only return ip6 when the
path from . to the zone in question is all ip6 accessible. i realize this is
wrong, as the path to the dns server is not the same as the path of the
packets, but, you know, should be a better hurestic than we've got today.
- erik
next prev parent reply other threads:[~2016-05-21 23:16 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
2016-05-21 23:16 ` erik quanstrom [this message]
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=8b9ac9787ef7d5263ae46a9e016943c9@lilly.quanstro.net \
--to=quanstro@quanstro.net \
--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).