You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When outputting with ndo_vflag > 0 IPv4 addresses have a newline before the IPs while IPv6 do not.
Here's an example:
1523520922.254050 IP (tos 0x0, ttl 107, id 4816, offset 0, flags [none], proto UDP (17), length 74)
@[email protected] > @[email protected]: [udp sum ok] 51092 A? example.com. (46)
1523520922.254978 IP6 (hlim 54, next-header UDP (17) payload length: 47) @[email protected] > @[email protected]: [udp sum ok]
This is a pretty minor issue, but it'd be nice if it was consistent. I wasn't sure if this was intentional or which way is preferred so that's why this is an issue instead of a pull request.
I vaguely remember a similar request a few years ago. It would indeed be nice to have the amount of newlines consistent, but if you think how many existing scripts this change would break, it will not look such a good idea.
When outputting with
ndo_vflag > 0
IPv4 addresses have a newline before the IPs while IPv6 do not.Here's an example:
This is a pretty minor issue, but it'd be nice if it was consistent. I wasn't sure if this was intentional or which way is preferred so that's why this is an issue instead of a pull request.
The newline comes from print-ip.c:468
Personally, I'd prefer a single line of output for easy parsing.
Forgot to mention: tcpdump version
4.9.2
and lippcap1.8.1
, but it doesn't look like the line in question has changed in newer versions.The text was updated successfully, but these errors were encountered: