[tcpdump-workers] Re: v4/v6 packet length printing inconsistency

2025-07-02 Thread Gert Doering
Hi, On Wed, Jul 02, 2025 at 03:28:59PM -0400, Michael Richardson wrote: > > Gert Doering wrote: > > I've been writing a document explaining inside/outside fragmentation in > > an OpenVPN context, explaining my points with "tcpdump", like this: > > > $ tcpdump -vv -i any host ... or

[tcpdump-workers] Re: v4/v6 packet length printing inconsistency

2025-07-02 Thread Michael Richardson
Gert Doering wrote: > I've been writing a document explaining inside/outside fragmentation in > an OpenVPN context, explaining my points with "tcpdump", like this: > $ tcpdump -vv -i any host ... or host ... ... > What is very obvious here is that for IPv4, there is a clear ind

[tcpdump-workers] Re: v4/v6 packet length printing inconsistency

2025-07-01 Thread Gert Doering
Hi, On Mon, Jun 30, 2025 at 06:03:49PM +0200, Gert Doering wrote: > How do you prefer to receive patches these days? MR on Github? Patch on > the list? (I'm a bit out of the loop wrt tcpdump contributions). So, I found CONTRIBUTING.md, and tried my best to follow it. The change is trivially s

[tcpdump-workers] Re: v4/v6 packet length printing inconsistency

2025-06-30 Thread Gert Doering
Hi, On Mon, Jun 30, 2025 at 08:43:29AM -0700, Guy Harris wrote: > To quote a comment I added to that issue: > > >> Personally, I'd prefer a single line of output for easy parsing. > > > > > > At one point, so did Apple, so they added a `-g` ("g" for "greppable") flag > > to remove that newline

[tcpdump-workers] Re: v4/v6 packet length printing inconsistency

2025-06-30 Thread Gert Doering
Hi, thanks for the background on this :-) On Mon, Jun 30, 2025 at 03:46:37PM +0100, Denis Ovsienko wrote: > If you prepare a pull request, please include a useful entry in the change > log. Will do. I'm not sure when I'll find time - what is the planned release date for 5.0? How do you prefer

[tcpdump-workers] Re: v4/v6 packet length printing inconsistency

2025-06-30 Thread Guy Harris
On Jun 30, 2025, at 8:43 AM, Guy Harris wrote: >> Perhaps we should implement that flag. > > ...and, if we do, and we split the lines in verbose mode for IPv6, the > -g/--ip-oneline flag would apply both to IPv4 and IPv6. If we implement the flag in the next 4.99.x release, that would allow pe

[tcpdump-workers] Re: v4/v6 packet length printing inconsistency

2025-06-30 Thread Guy Harris
On Jun 30, 2025, at 7:46 AM, Denis Ovsienko wrote: > 1: https://github.com/the-tcpdump-group/tcpdump/issues/810 To quote a comment I added to that issue: >> Personally, I'd prefer a single line of output for easy parsing. > > > At one point, so did Apple, so they added a `-g` ("g" for "greppa

[tcpdump-workers] Re: v4/v6 packet length printing inconsistency

2025-06-30 Thread Denis Ovsienko
On Mon, 30 Jun 2025 11:47:16 +0200 Gert Doering wrote: > So - if I were to send a patch to change IPv6 printing to be similar > to IPv4 (dual-line, and overall packet length) would this be something > you are interested in? Or is someone already working on it, per > chance? Hello Gert. The in