Skip to content

tcpdump(1): Update the NAME section with "other capture devices"#1417

Open
fxlb wants to merge 1 commit into
the-tcpdump-group:masterfrom
fxlb:man
Open

tcpdump(1): Update the NAME section with "other capture devices"#1417
fxlb wants to merge 1 commit into
the-tcpdump-group:masterfrom
fxlb:man

Conversation

@fxlb

@fxlb fxlb commented Feb 26, 2026

Copy link
Copy Markdown
Member

tcpdump is able to capture on devices that libpcap implements by means other than the OS network stack: e.g. Bluetooth, D-Bus, and USB.

[skip ci]

tcpdump is able to capture on devices that libpcap implements by means
other than the OS network stack: e.g. Bluetooth, D-Bus, and USB.

[skip ci]
@guyharris

Copy link
Copy Markdown
Member

"other communications medium"?

@fxlb

fxlb commented Feb 26, 2026

Copy link
Copy Markdown
Member Author

"other communications medium"?

Why not? Any other suggestions?

@fxlb

fxlb commented Feb 26, 2026

Copy link
Copy Markdown
Member Author

"other supported interfaces" ?

@fxlb

fxlb commented Feb 26, 2026

Copy link
Copy Markdown
Member Author

"dump packets on a network or other supported interfaces"?

@guyharris

Copy link
Copy Markdown
Member

The current language speaks of capturing on a "network" rather than on a "device".

If we continue to use "network", we should probably speak of capturing on a communications medium rather than on a device/interface/whatever.

If we speak of capturing on a "device"/"network interface"/whatever, we can speak of capturing on other devices.

It's not clear that tcpdump (or Wireshark or any other capture tool) captures on a "network" - if it's a single network segment, then what it captures is the packed that the adapter is set up to capture and that it can capture (so if you're not capturing in promiscuous mode, or you're on a switched network and not plugged into a sniffer port on the switch, you're not capturing all traffic on the network segment), and you're also not capturing on the entire network (I can't see your traffic to the Internet if I capture on our Wi-Fi network :-)).

So I'm not sure which language is appropriate.

@fxlb

fxlb commented Feb 26, 2026

Copy link
Copy Markdown
Member Author

Good questions.
in DESCRIPTION, we have:
tcpdump prints out a description of the contents of packets on a network interface [...]

@fxlb

fxlb commented Feb 26, 2026

Copy link
Copy Markdown
Member Author

"dump packets on libpcap-supported interfaces and devices"

@fxlb

fxlb commented Feb 27, 2026

Copy link
Copy Markdown
Member Author

"Protocol analyzer"

@infrastation

Copy link
Copy Markdown
Member

Network protocol analyzer.

@infrastation

Copy link
Copy Markdown
Member

Or rather "network packet analyzer" because most of the time tcpdump does not relate different packets together.

@fxlb

fxlb commented Feb 28, 2026

Copy link
Copy Markdown
Member Author

I try to avoid network only e.g. USB.

@infrastation

Copy link
Copy Markdown
Member

There is a number of other archaisms (e.g. all packets on the net will be dumped), this has been improving slowly one word/sentence/paragraph at a time, but obviously needs more work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

3 participants