From Section 2.2 of the path specification
We do not choose any router in the same family as another in the same path. (Two routers are in the same family if each one lists the other in the "family" entries of its descriptor.)
On more than one occasion I've had to manually create a
NodeFamily from the results of Atlas. In each case the node has a family but appears to ignore it during path selection. That is, until I create the family manually. This occurs with
StrictNodes using Tor v0.2.5.10.
In a related incident, despite the use of
StrictNodes, an exit was used which violated constraints put into effect. Now I can understand being flexible in choosing to violate (some) constraints. If I say I don't want an exit to be used and I use
StrictNodes, then the exit shouldn't be used.
Should I be concerned or is there a good reason for this to occur?