Hi Aaron,
I see what you mean. I'm using pcapio.[ch] in dumpcap,
so I'm using WTAP_ENCAP_PER_PACKET...
Can you file a bug report at https://bugs.wireshark.org/bugzilla/
such that it does not get forgotten. Please describe
what you want to get working (possibly providing the
input file). Then it does not get lost.
I will look at it after finishing the capturing support,
if no one else takes the issue earlier.
Best regards
Michael
On May 21, 2009, at 9:34 PM, Aaron Turner wrote:
On Thu, May 21, 2009 at 12:20 PM, Michael Tüxen
<Michael.Tuexen@xxxxxxxxxxxxxxxxx> wrote:
On May 21, 2009, at 9:15 PM, Aaron Turner wrote:
On Thu, May 21, 2009 at 11:55 AM, Michael Tüxen
<Michael.Tuexen@xxxxxxxxxxxxxxxxx> wrote:
Hi Aaron,
can you check also with the latest svn version?
This was trunk-1.0 r28436. Are you working in trunk (wireshark
1.1.x)?
Yes, I'm working in 1.1.x...
I just looked at the lastest trunk, and it too hard codes only
ethernet as supported:
from wiretap/pcapng.c pcapng_dump_can_write_encap():
/* XXX - for now we only support Ethernet */
if (encap != WTAP_ENCAP_ETHERNET)
return WTAP_ERR_UNSUPPORTED_ENCAP;
--
Aaron Turner
http://synfin.net/
http://tcpreplay.synfin.net/ - Pcap editing and replay tools for
Unix & Windows
Those who would give up essential Liberty, to purchase a little
temporary
Safety, deserve neither Liberty nor Safety.
-- Benjamin Franklin
___________________________________________________________________________
Sent via: Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
Archives: http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe