From: Jakub Sitnicki <j...@redhat.com> Date: Sun, 30 Oct 2016 14:03:11 +0100
> 2) ensure the flow labels used in both directions are the same (either > reflected by one side, or fixed, e.g. not used and set to 0), so that > the 4-tuple we hash over when forwarding, <src addr, dst addr, flow > label, next hdr>, is the same both ways, modulo the order of > addresses. Even Linux, by default, does not do reflection. See the flowlabel_consistency sysctl, which we set by default to '1'. I think we need to think a lot more about how systems actually set and use flowlabels. Also, one issue I also had with this series was adding a new member to the flow label. Is it possible to implement this like the ipv4 side did, by simply passing a new parameter around to the necessary functions? Thanks.
