On 10 December 2015 at 14:20, Pravin Shelar wrote:
> On Tue, Dec 8, 2015 at 4:14 PM, Joe Stringer wrote:
>> If userspace executes ct(zone=1), and the connection tracker determines
>> that the packet is invalid, then the ct_zone flow key field is populated
>> with the default zone rather than the
On Tue, Dec 8, 2015 at 4:14 PM, Joe Stringer wrote:
> If userspace executes ct(zone=1), and the connection tracker determines
> that the packet is invalid, then the ct_zone flow key field is populated
> with the default zone rather than the zone that was specified. Even
> though connection trackin
If userspace executes ct(zone=1), and the connection tracker determines
that the packet is invalid, then the ct_zone flow key field is populated
with the default zone rather than the zone that was specified. Even
though connection tracking failed, this field should be updated with the
value that us
