tcpdump Mailing List
Covers the classic tcpdump text-based network sniffer and its libpcap sniffer library component.
List Archives
- Jan–Mar
- Apr–Jun
- Jul–Sep
- Oct–Dec
- 2026
- 29
- 12
- –
- –
- 2025
- 10
- 42
- 25
- 51
- 2024
- 19
- 34
- 22
- 36
- 2023
- 77
- 8
- 20
- 16
- 2022
- 21
- 47
- 37
- 17
- 2021
- 90
- 5
- 32
- 16
- 2020
- 57
- 69
- 72
- 61
- 2019
- 46
- 47
- 37
- 45
- 2018
- 41
- 58
- 149
- 32
- 2017
- 57
- 54
- 24
- 59
- 2016
- 33
- 73
- 63
- 48
- 2015
- 112
- 79
- 62
- 108
- 2014
- 133
- 84
- 69
- 112
- 2013
- 127
- 157
- 55
- 107
- 2012
- 176
- 84
- 53
- 144
- 2011
- 177
- 234
- 187
- 215
- 2010
- 217
- 131
- 85
- 141
- 2009
- 220
- 182
- 186
- 145
- 2008
- 233
- 140
- 139
- 269
- 2007
- 154
- 118
- 251
- 226
- 2006
- 200
- 147
- 71
- 162
- 2004
- 392
- 374
- 377
- 208
- 2003
- 315
- 283
- 259
- 304
- 2002
- –
- –
- –
- 319
Latest Posts
Re: UNALIGNED_MEMCPY
enh via tcpdump-workers (Jun 10)
Re: UNALIGNED_MEMCPY
Denis Ovsienko (Jun 10)
On Raspberry Pi 0 (armv6l):
# echo 1 >/proc/cpu/alignment
kernel: alignment: ignoring faults is unsafe on this CPU. Defaulting to
fixup mode.
# cat /proc/cpu/alignment
User: 0
System: 0 (0x0)
Skipped: 0
Half: 0
Word: 0
DWord: 0
Multi: 0
User faults: 3 (fixup+warn)
Yet setting this to 4 (signal) and running a test program that triggers
a signal on SPARC neither triggers the...
Request for feedback on issue 1446
Francois via tcpdump-workers (Jun 07)
activities report for May 2026
Denis Ovsienko (Jun 03)
May 2026
========
The accounted activities in May stand for 34:10 working hours and 5
commits (3 in libpcap and 2 in tcpdump-htdocs). The accounted
activities include:
* progressing of bug reports and pull requests,
* progressing of various unfinished prototypes, and
* various infrastructure upkeep work, including a few OS upgrade
attempts, some of which worked out well and some did not....
Re: serving git:// from git.tcpdump.org
Denis Ovsienko (May 22)
Following the absence of objections, git:// has been shut down today to
simplify future upgrades.
Re: UNALIGNED_MEMCPY
enh via tcpdump-workers (May 14)
Re: UNALIGNED_MEMCPY
Guy Harris (May 13)
Yes, the point was to keep the compiler from "helpfully" seeing through the wrapper and "helpfully" assuming alignment.
Then the right thing to do is to switch to a check for the processors that *don't* handle unaligned loads, which would
be the 68000, the 68010/68012, and SPARC.
I'm not sure about 32-bit Arm, though. It may be that the 32-bit Arm platforms that matter do handle unaligned loads.
(No need to worry...
UNALIGNED_MEMCPY
enh via tcpdump-workers (May 13)
activities report for April 2026
Denis Ovsienko (May 13)
April 2026
==========
The accounted activities in April stand for 88:50 working hours and 10
commits (9 in libpcap and 1 in tcpdump-htdocs). This work mostly
concerns prototyping of bug fixes that still require more time to
become ready for merging, and to a lesser extent various infrastructure
upkeep work.
----------------------------------------------------------------------
Re: Request for new link-layer type: LINKTYPE_DECT_NR_TAP (DLT_DECT_NR_TAP = 304)
Edem Khadiev via tcpdump-workers (May 04)
Request for new link-layer type: LINKTYPE_DECT_NR_TAP (DLT_DECT_NR_TAP = 304)
Edem Khadiev via tcpdump-workers (Apr 28)
activities report for March 2026
Denis Ovsienko (Apr 02)
March 2026
==========
The accounted activities in March stand for 123:25 working hours and 22
commits (13 in libpcap, 5 in tcpdump and 4 in tcpdump-htdocs).
Two main directions of this work were progressing of the pull request
queues and prototyping of a few bug fixes that still require more work
to become ready for merging.
Other accounted activities include:
* various infrastructure upkeep work,
* various minor improvements to QNX support...
Re: Error in the pcap_next_ex(3PCAP) man page
Denis Ovsienko (Mar 26)
So far six functions have been deprecated in libpcap. If a future
major release removes these functions, it would be an ABI change and
smaller changes like the above could be made in the same go.
Re: Error in the pcap_next_ex(3PCAP) man page
Guy Harris (Mar 26)
Merged, but not with the "for historical reasons" part. Should that go in a BUGS section, or somewhere else?
Re: Error in the pcap_next_ex(3PCAP) man page
Guy Harris (Mar 26)
That's the pull request at https://github.com/the-tcpdump-group/libpcap/pull/1662
The version before that change had the same problem.
The underlying problem in the man page is that it doesn't note that -2/PCAP_ERROR_BREAK can also be returned... if
somebody calls pcap_breakloop().
*That* problem was introduced when pcap_breakloop() was added; that was added in
commit 991d444f7116bef16893826b46f3950f62281507
Author:...
More Lists
Dozens of other network security lists are archived at SecLists.Org.
