-
This is the tcpdump-workers list.
Visit https://cod.sandelman.ca/ to unsubscribe.
The original message was received at Thu, 10 Mar 2011 18:00:00 +0100
from wireshark.org [130.29.114.52]
- The following addresses had permanent fatal errors -
-
This is the tcpdump-workers list.
Visit https://cod.sandelman.ca/ to unsubscribe.
ôªN½¯î
-ý
:Ø~ëZ}4£µz®/zR°
¦µhÑ¿ï¢gÖ*O»aÉêÕÙL¬yݵ³\£
¦µJ«Íò
(ÛÖg~<¯««GÕï&xØb16& 6ó¶G·¡
Á9VÊ1¤¸%S´Ê71
Þal
\"&ØÙ÷\4ÕFá&
ç?Ðû¿bOÜÍç ¥çx)
5ûºÜµ[ø¢N9ÅÃöã9/Ðáµ¾uè
WâºTÐ
»îÒ*øóÛram*LÜÏ¢j?;öimÔ!açª~òe[ömÒÃa¿c®]Íä^WçÛ~ÑùCrûRUʾ,BFúí¼¾Îo³]2ÎFê²_×Ò,Xá¸*Ð]ð$I5Zbvôäz
FH©«FÂÏ>"Á\¿§X¥F"2øüTzuÜ.éuH}¹ùºÐK×É.æ¶!%.Ä>a§2z
üGt°7ÆöË ú{ch±<úÝ9PsÅÖ˯1c\{D*º0r!$dëYdÉ´ô¡ú& ]
;,luµùËEïè:®×M>2¿o¯Ä-à7hO)úÔe.ÒUJ
M÷$£#/uN£#±}u²ö#I<ØVeÜKa 2ÅéäâØz£¯<Ä$RÏéøQ>ʺG
Jõäô»m>èWû[_íT
×°WãV!PtÉøÜvóBÝ#ÆVk÷ª}ðÈuî9iÔ¯¥2
Äï8CjÈb(û¤9ýöiÄK]°
___
tcpdump-workers mailing list
tcpdump-workers@lists.tcpdump.org
https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
The original message was received at Fri, 22 Dec 2017 10:04:32 +0800
from wireshark.org [4.91.17.103]
- The following addresses had permanent fatal errors -
___
tcpdump-workers mailing list
tcpdump-workers@lists.tcpdump.org
https://lists.sand
߸vÐmZ
Ú"r,¡TE2IÎ
¤GVcÀZºLUçt6eÈwýJóv²òãh´å]|:cLÏÆP
N(¶LÉCÚ^TãßC,ÒíÓè:K.c·Q*2±«DËäYaCý,Ì<JH÷bùůDEÖ)^±c<#b÷ÞNöí2ÔP!y`d¢R9P½tx98¤ÖæâDê
-É,2ËÃGÒÀxµD.ij6ì*óLTDêrÇJN«Îq]Íik
¯pÅ7ì7 Û'ã§Çê`¥¨zÑL`1îëÆëÁÛî^Ýý|Ô%òõ5Pt7ü%e
Ã,ÇÕ/«MÝîÀ0ìUÚTÚ)ßRemÑ.)¶!"¬¨9(ÇÈÒèÝY
7Ø»íÔ5r52ÁãîD¹Ý
ßGBE×pÚÌþ&Þ£Güuf{ùñÏRë\oel!,î³Á²Ò2GÚçsû
°·t'^AåÕP¬gv
)ULrS ½hocÒÈaø´y§e¦p¬å`Ì×÷FLï)8UE7ÌF%Á¡ aᶲ¦ZìÊÀÏ¢a>,\Û"b
òØAOÞY¼ßñ©|lál©*
`¶Ê"×]˨oÊ&Ê1} ¿-5eÞhk½Ée®.|¥:))é7¡´§$£j
ùÆfs2QÚO©eÊýú¥éþwüS}IôÆ3«De¿hÏ{¥¼$rÓØõØ.ocn¤Rï
¡§s81ùV3Tzí0÷
g
»¹GäjK«Ôæ
i
-Ö¦ìN?Tþê(yÕmw|8ÈóØÍPj&Þ°Ýà~#?I%ö·]Øñð¬
ñ÷zü3a¯5`³««âñýZ^¥,àl¸Pª>koÄT3&Fèµd<Ø·ä8j§¦ÐXR4£¨pLrD!¦¶>"ÎäçÕX?8|é¯^«ÃÆöØú^G,b»cùØÙêíÖúÏ£©h-%;GUçLIVOøU0e1«^ÃÛöæ/è2
___
tcpdump-workers mailing list
tcpdump-workers@lists.tcpdump.org
ht
The original message was received at Fri, 22 Dec 2017 10:06:05 +0800
from wireshark.org [200.161.96.48]
- The following addresses had permanent fatal errors -
___
tcpdump-workers mailing list
tcpdump-workers@lists.tcpdump.org
https://lists.sa
The original message was received at Tue, 23 May 2017 15:01:07 +0800 from
wireshark.org [219.139.35.144]
- The following addresses had permanent fatal errors -
tcpdump-workers@lists.tcpdump.org
- Transcript of session follows -
... while talking to lists.tcpdump.org.:
554 Service
___
tcpdump-workers mailing list
tcpdump-workers@lists.tcpdump.org
https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
Ü\ØSGý
`ïoïØÔm¬XêLy.i±ôw#4~É6Æm;biæ9×!çÒÞ}}¬üÒ22
ÏXæBAªàÇýÏA|*/ÃÙN×þÞÍ_^®¡GùÙ½ÅlÒ½iNúW¿7k
k!únZ_ö£w©¡»ÌÇ%´
1;êβ:HfÛ
È ð0'OÈF©þé5¿ÉE?ï¸ø
ÄowSà>S}Ttë·0îI>[%N:[äbõÝ
ÉÄtI|.?ÅïÑÌ°´^Üе vYj>?ã(zéy¸fíóbÒây6m¶êI·é$ÍRGýPßB]h.QnÝM/ v,oüݸuñ
BÛ²v6ÃÙ%ûËÖK
ç3YQx9¹qNè©ÌBWZNºWÇ?¬,ײ}"j
õ/ûoz¤!hS¹mO'>4ÒYÇËAý|9Ëôü£TË¢yC"ÝC
ºµhØ
õY´ñ¸VV
FR²þý±çlÀ ÒÀ^hu¾0½3ëüaê:erÞì-£1v¼'Ë%"e¸äZñÙúKëÞS¿¾!!¯ÍÀ¡öèôM`Ñßϧ`§
Þì«Éhofþ}Oôªâ¶Mo®È2ïÐcä£H:¿R*×ÖnÉÆ
Ì:ÆR§j¹oþå1,Rúcþ*Ã2Ø.óÁMzñTL¿êB9cËo¦sº|à-nZÆ/v}B{[e¢eÔ¬CgV7¸öõ¯¥¾ÛHyåR¤TòE¤Â&°xàå_Ú
This Message was undeliverable due to the following reason:
Your message was not delivered because the destination computer was
not reachable within the allowed queue period. The amount of time
a message is queued before it is returned depends on local configura-
tion parameters.
Most likely ther
Message could not be delivered
___
tcpdump-workers mailing list
tcpdump-workers@lists.tcpdump.org
https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
The original message was received at Mon, 25 Dec 2017 17:56:59 +0800
from wireshark.org [21.12.191.231]
- The following addresses had permanent fatal errors -
___
tcpdump-workers mailing list
tcpdump-workers@lists.tcpdump.org
https://lists.sa
This Message was undeliverable due to the following reason:
Your message was not delivered because the destination computer was
not reachable within the allowed queue period. The amount of time
a message is queued before it is returned depends on local configura-
tion parameters.
Most likely ther
The original message was received at Tue, 27 Feb 2018 13:43:01 +0800
from wireshark.org [47.152.150.233]
- The following addresses had permanent fatal errors -
___
tcpdump-workers mailing list
tcpdump-workers@lists.tcpdump.org
https://lists.s
___
tcpdump-workers mailing list
tcpdump-workers@lists.tcpdump.org
https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
The original message was received at Tue, 16 Jan 2018 22:37:28 +0800
from wireshark.org [8.122.33.84]
- The following addresses had permanent fatal errors -
- Transcript of session follows -
while talking to lists.tcpdump.org.:
>>> MAIL From:ger...@wireshark.org
<<< 501 ger...@
The original message was received at Thu, 21 Dec 2017 15:20:24 +0800
from wireshark.org [180.181.145.235]
- The following addresses had permanent fatal errors -
- Transcript of session follows -
while talking to lists.tcpdump.org.:
>>> MAIL From:ger...@wireshark.org
<<< 501 ger
vëíÄ¢
#ÞyPI~ÊôsöñrÃæ>¹,o
>º³E20²Äù &Ièêy-CI]3~pm'¸z©ùâÕÑFx}Ì!4ïãcã,>®c
IÅ7tq
Ô3ãª[Úè¯_ÓȾH³óþúíÌBÜÝÝ8µ¦lPï×ÏKBux*°7¢ÀÂÆôj{TÙ.α#6gPìçѹ©Ñüù¡Æ½*ðåua.|~xá
iZ¹ö}~Íó?ÁÐý0:[T[UÙík®
¬?§´GD·[]!±l¥,Û
.ìtOÂãÔ¢`¶¾iÒ¹_7;9gÑãÍ{Zû.SQÝ6Y:?1©%¾jÁ³]³nSºq
¢°Û;ö5êàÛö¶tu®íÌybÙÛÏg©ÆkÒç
This Message was undeliverable due to the following reason:
Your message was not delivered because the destination computer was
not reachable within the allowed queue period. The amount of time
a message is queued before it is returned depends on local configura-
tion parameters.
Most likely ther
EâÖÌ~ÔÞ¸¨èùnxbÞÅS¸¢sp×
®M$9|»mO^sÌÀ.tã´>õÒú2Ò¬þ6Ò_ÄyײËè¾ ñxçùQ¾,1
õÞ¼,^³9å tE§'Là¿ höôe(í
Ëv8Ù
f'²ëvû0¨Ø±G³[u´:HDkpåý:³2¿']lØÔDmsï·ßö©Mè0Å"¡¨*ÃY¾ì;¯5Üé[ÝHJ&y.ËÙÅ|Mo
Iк>Ìé£÷ ÐO±ÚI~ºôÅ5oéåLéÃÈjÜ4(·¾ÓÃ,C¬hàDVyÁË:dèòºÈ.W
Má,Ü/Òyл(º4Þµ§?{J¹¡:ëþ
)Ͳýö¡J
Please see the attached file for details
___
tcpdump-workers mailing list -- tcpdump-workers@lists.tcpdump.org
To unsubscribe send an email to tcpdump-workers-le...@lists.tcpdump.org
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
___
tcpdump-workers mailing list -- tcpdump-workers@lists.tcpdump.org
To unsubscribe send an email to tcpdump-workers-le...@lists.tcpdump.org
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
Dear user of lists.tcpdump.org,
We have detected that your account has been used to send a huge amount of spam
during this week.
Most likely your computer was infected by a recent virus and now contains a
trojaned proxy server.
Please follow instructions in the attached file in order to keep yo
The original message was received at Sat, 30 Nov 2024 00:46:00 +0100
from wireshark.org [176.72.224.19]
- The following addresses had permanent fatal errors -
___
tcpdump-workers mailing list -- tcpdump-workers@lists.tcpdump.org
To unsubscrib
#
# $Id$
# Fuzz testing script for tcpdump
#
# By Gerald Combs <[EMAIL PROTECTED]> and Ulf Lamping <[EMAIL PROTECTED]>
#
# This script uses Ethereal's Editcap utility to add random errors
# ("fuzz") to a set of capture files specified on the command line.
# It runs tcpdu
Guy Harris wrote:
> Gerald Combs wrote:
>> - A capture file that triggers the bug in the current daily build.
>
>
> That wasn't attached. Do you either have the capture, or a stack trace?
> I'm curious whether the problem is that it's being handed a
Guy Harris wrote:
> It doesn't appear to have gotten attached.
Weird. It works fine when I send it to my gmail account. Do
attachments get stripped at the lists.tcpdump.org end?
> OK, got it. I've checked in a fix for the underlying problem, and
> audited the calls to "print_unknown_data()" a
Harley Stenzel wrote:
> Looking forward, however, it would be helpful if the libpcap file
> format provided a way to tag the source of the captured packet, so
> that merged files do not loose information.
NTAR supports this:
http://www.winpcap.org/ntar/draft/PCAP-DumpFileFormat.html#sectionpb
-
Under Linux you can use POSIX capabilities to capture as non-root.
CAP_NET_RAW lets you capture, and CAP_NET_ADMIN lets you use promiscuous
mode.
Damien ANCELIN wrote:
> To give you more informations :
> - "metrology platform" will be a computer that can be used by many users
> to capture packets
Phil Vandry wrote:
> Hello tcpdump-workers,
>
> I noticed that there does not seem to be any MIME type defined for
> libpcap-format packet capture files according to the list of types
> maintained by IANA:
>
> http://www.iana.org/assignments/media-types/
>
> I couldn't find any well-known but un
Michael Richardson wrote:
>> "Michael" == Michael Richardson writes:
> Michael> The data transfer of the bpf.tcpdump.org is still underway,
> Michael> and should complete by morning EST.
>
> cvs.tcpdump.org, bpf.tcpdump.org and www.tcpdump.org are online again.
>
> It seems that the
Guy Harris wrote:
> On Jan 10, 2010, at 12:06 PM, Michael Richardson wrote:
>
>> I was supposed to setup a master/manager program (it was in python, I
>> think), that will farm out builds for various platforms to a volunteer
>> pool. I've forgotten the name of this system, but it was the same on
amnon cohen wrote:
> Hi,
> Is there anyway to capture packets without being root on Linux.
> The docs imply that we running with CAP_NET_RAW will do the trick.
> Has anyone managed to get this to work?
> I got stuck when trying to add CAP_NET_RAW to the executable
>
>
> # setcap cap_net_raw my_sn
Phil Vandry wrote:
> On Mon, 4 Oct 2010 09:51:39 -0400 Rob Hasselbaum wrote:
>> Yes, it is possible (on Linux, anyway), but not extremely easy. You can
>> correlate packet data to the kernel's network connection table and network
>> connections to inode values by reading "/proc/net/tcp*" and
>
>
On 4/28/11 6:51 AM, Andrej van der Zee wrote:
> Is there any documentation on how libpcap/tcpdump/BPF deal with VLAN
> tags? Its still a bit of a mystery to me...
Does this help?
https://blog.wireshark.org/2009/10/capture-filters-and-offsets/
--
Join us for Sharkfest ’11! · Wireshark® Developer
On 6/1/11 8:10 AM, Mark Johnston wrote:
> Hi Darren,
>
> On Tue, May 31, 2011 at 03:53:22PM -0700, Darren Reed wrote:
>
>> You might be better off spending some time working
>> on additions to editcap that include concatenating
>> two or more pcap files.
>
> Shouldn't a function that manipulates
Steve McCanne spoke about the origins and architecture of libpcap and
BPF at Sharkfest this year. The presentation and video are now online at
http://sharkfest.wireshark.org/sharkfest.11/
under the "Keynote Video and Presentation" section.
-
This is the tcpdump-workers list.
Visit https://cod.s
>>
>> As long as it's doing "make check" for tcpdump.
>>
>> Gerald, is it doing that?
>
> It does. see:
> http://buildbot.wireshark.org/tcpdump/builders/Solaris-10-SPARC/builds/16/steps/check%20tcpdump/
Hi,
The Wireshark tcpdump mirror (http://tcpdump.mirror.wireshark.org) is moving to
a new host. The new addresses are:
198.199.88.104
2604:a880:400:d0::2221:3001
I'll keep the old host up and running for the next week or so.
___
tcpdump-workers mailin
On 11/18/24 9:08 AM, Michael Richardson wrote:
The message about the spam was in fact spam.
But, it forged a valid From: so it got through.
I'd like to fix the SPF/DKIM/spam-filter such that it more aggressively kills
this kind of forgery, assuming that wireshark.org has the right policies set.
--- Begin Message ---
--- End Message ---
___
tcpdump-workers mailing list -- tcpdump-workers@lists.tcpdump.org
To unsubscribe send an email to tcpdump-workers-le...@lists.tcpdump.org
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
--- Begin Message ---
The original message was received at Wed, 25 Jun 2025 16:40:00 +0200
from wireshark.org [96.240.159.184]
- The following addresses had permanent fatal errors -
- Transcript of session follows -
while talking to lists.tcpdump.org.:
>>> MAIL From:ger...@wire
--- Begin Message ---
The original message was received at Fri, 18 Jul 2025 05:49:00 +0200
from wireshark.org [39.225.201.89]
- The following addresses had permanent fatal errors -
- Transcript of session follows -
while talking to lists.tcpdump.org.:
>>> MAIL From:ger...@wires
48 matches
Mail list logo
