Hi tcpdump folks,
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 ...
11:43:48.930177 tun2 Out IP6 (flowlabel 0xa3885, hlim 64, next-header ICMPv6
(58) payload leng
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
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
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
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
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
