> 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
