On Mon, 2011-11-28 at 14:35 -0500, abhinav narain wrote:
> I don't think I can use "any" interface as it might capture packets from
> bridge interface also !
I use bonding to re-combine traffic from the Tx and Rx of a passive
optical tap. You might be able to use the same technique. Here is an
ex
size is large then
traffic analysis is effective.
--
Glen Turner
www.gdt.id.au/~gdt
-
This is the tcpdump-workers list.
Visit https://cod.sandelman.ca/ to unsubscribe.
On Fri, 2011-04-01 at 21:47 +1030, Glen Turner wrote:
> For those with files like /etc/mime.types, you may wish to add the line:
> application/vnd.tcpdump.pcap pcap
Looking at Debian bug 620372 reported by Gerald Combs, if
Debian's /etc/mime.types were to read
application/vnd.t
vnd.tcpdump.pcap
Best wishes to all, Glen
--
Glen Turner
www.gdt.id.au/~gdt
-
This is the tcpdump-workers list.
Visit https://cod.sandelman.ca/ to unsubscribe.
On 11/11/10 22:48, Claudio Peldoza wrote:
hello, my english no very good, but try.
I need rpm libpcap 1.0.0 to centos 5.5.
may send the package to install on my server?.
Perhaps the easiest way to move to more recent software is to rebuild a libpcap package from Fedora
on your CentOS 5.5 machi
f the captured packet" - the
> link-layer headers in question are "bytes of the captured packet" in
> that they're in the blob of data libpcap hands you as the packet data,
> but do need to be byte-swapped.
Yep, will fix.
> Hopefully they won't get upse
"vnd.tcpdump.org-libpcap" was
problematic, as some applications parse MIME types using the "." as a
separator. Apparently I should not anticipate issues with "tcpdump" as
the vendor/product name.
Are there further comments on this Version 2 of this proposal?
Your Name:
[Gl
f a fellow standards organisation like OASIS preferred not to bother with the
IANA hoops for a IETF standard MIME type for OpenDocument, then there's a hint for smaller projects :-)
--
Glen Turner <http://www.gdt.id.au/~gdt/>
-
This is the tcpdump-workers list.
Visit https://cod.sandelman.ca/ to unsubscribe.
r Name:
[Glen Turner]
Your Email Address:
[...@___.__.__]
1. Media Type Name:
See RFC 2046 section 3, and RFC 2077.
[application]
2. Subtype name (See Existing subtype names)
See also RFC 2046, and RFC 4288, sections 3 and 4.2.
Note: Registrations in the standards tree must be approved
Hi Guy,
Is that a problem with said requirements?
The IANA mandatory requirements for vendor MIME types are:
- they must reference media, not other things
- syntax must be correct
- parameters must be explained (there are none in this case)
- each MIME type describes only one data format,
ration
AddType application/vnd.tcpdump.org-libpcap .pcap .cap .dmp
AddDescription "Network packet capture" .pcap .cap .dmp
--
Glen Turner <http://www.gdt.id.au/~gdt/>
-
This is the tcpdump-workers list.
Visit https://cod.sandelman.ca/ to unsubscribe.
11 matches
Mail list logo