Re: [tcpdump-workers] One of these things is not like the others

Guy Harris wrote: >> Guy Harris wrote: >> >>> Note that macOS's tcpdump has a -g flag ("g" for "greppable", more >>> greppable output being the purpose of the flag), which puts the IPv4 >>> input back on one line: >> >> How can we move to this format? > To make

Re: [tcpdump-workers] One of these things is not like the others

On May 24, 2017, at 10:36 AM, Michael Richardson wrote: > Guy Harris wrote: > >> Note that macOS's tcpdump has a -g flag ("g" for "greppable", more >> greppable output being the purpose of the flag), which puts the IPv4 >> input back on one line: > > How can we move to this format? To make th

Re: [tcpdump-workers] One of these things is not like the others

Guy Harris wrote: > Is there some reason why, with -v, IPv4 packets are printed on two > lines and IPv6 packets are printed on one line? I don't think so. > Note that macOS's tcpdump has a -g flag ("g" for "greppable", more > greppable output being the purpose of the flag), which

[tcpdump-workers] One of these things is not like the others

04:11:18.046715 IP (tos 0x0, ttl 64, id 35811, offset 0, flags [DF], proto TCP (6), length 48) 192.168.119.11.41249 > 195.115.97.196.80: Flags [S], cksum 0xcc57 (correct), seq 358236700, win 24820, options [nop,nop,sackOK,mss 1460], length 0 06:45:19.021820 IP6 (hlim 64, next-header TCP (6)