Re: [PATCH v2 nft] parser: tcpopt: fix tcp option parsing with NUM + length field

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: [PATCH v2 nft] parser: tcpopt: fix tcp option parsing with NUM + length field
From: Thomas Haller <thaller@xxxxxxxxxx>
Date: Wed, 06 Dec 2023 08:58:43 +0100
Cc: Maciej Żenczykowski <zenczykowski@xxxxxxxxx>
In-reply-to: <20231205115610.19791-1-fw@strlen.de>
User-agent: Evolution 3.50.1 (3.50.1-1.fc39)

Hi Florian,

On Tue, 2023-12-05 at 12:56 +0100, Florian Westphal wrote:
>  .../packetpath/dumps/tcp_options.nft          | 14 +++++++

is there a reason not to also generate a .json-nft file?


Thomas

Follow-Ups:
- Re: [PATCH v2 nft] parser: tcpopt: fix tcp option parsing with NUM + length field
  - From: Florian Westphal

References:
- [PATCH v2 nft] parser: tcpopt: fix tcp option parsing with NUM + length field
  - From: Florian Westphal

Prev by Date: Re: [PATCH nft v2 0/5] add infrastructure for unit tests
Next by Date: Re: [PATCH] ipvs: add a stateless type of service and a stateless Maglev hashing scheduler
Previous by thread: Re: [PATCH v2 nft] parser: tcpopt: fix tcp option parsing with NUM + length field
Next by thread: Re: [PATCH v2 nft] parser: tcpopt: fix tcp option parsing with NUM + length field
Index(es):
- Date
- Thread

[Index of Archives] [Netfitler Users] [Berkeley Packet Filter] [LARTC] [Bugtraq] [Yosemite Forum]

Powered by Linux