> On Aug 21, 2018, at 11:17 PM, Toke Høiland-Jørgensen wrote:
>>
>> Well that’s good timing for me as I’m wrapping up a small utility/eBPF
>> to classify an arbitrary username to either MAC or IP. Here’s the work
>> in progress, which is not done yet as flow fairness is still under
>>
On 21 August 2018 23:06:11 CEST, Pete Heist wrote:
>
>> On Aug 21, 2018, at 1:25 PM, Toke Høiland-Jørgensen
>wrote:
>>
The next simplest fix is to ignore the flow ID override unless
>we're
in "flows" mode. We can then make valid assumptions about what
>should
go into the host
> On Aug 21, 2018, at 1:25 PM, Toke Høiland-Jørgensen wrote:
>
>>> The next simplest fix is to ignore the flow ID override unless we're
>>> in "flows" mode. We can then make valid assumptions about what should
>>> go into the host tables.
>>>
>>> The *right* fix, if we want to maximise
>> The next simplest fix is to ignore the flow ID override unless we're
>> in "flows" mode. We can then make valid assumptions about what should
>> go into the host tables.
>>
>> The *right* fix, if we want to maximise functionality, would be to
>> pass the result struct by reference into
