> On May 21, 2016, at 10:04 AM, erik quanstrom <quans...@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.
