usbmon broken
Bug #523340 reported by
Pekka Pessi
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
libpcap (Debian) |
Fix Released
|
Unknown
|
|||
libpcap (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Lucid |
Won't Fix
|
Medium
|
Unassigned |
Bug Description
The libpcap 1.0.0 traces from usbmon fail because libpcap does not take into account 16 extra padding bytes present in the mmap interface used in Linux kernels 2.6.21 and later.
Problem is fixed in libpcap development version, but it can be circumvented in 1.0.0 if libpcap avoids using mmap interface.
This bug makes tracing USB devices with wireshark and tcpdump effectively useless.
TEST CASE:
See comment #3 (https:/
tags: | added: patch |
Changed in libpcap (Debian): | |
status: | Unknown → Fix Committed |
Changed in libpcap (Debian): | |
status: | Fix Committed → Fix Released |
description: | updated |
Changed in libpcap (Ubuntu Lucid): | |
milestone: | none → lucid-updates |
status: | New → Triaged |
importance: | Undecided → Medium |
To post a comment you must log in.
I'd like to help out fixing this bug and 523349 but I'm really not quite certain how to test this. Is testing it using wireshark and usb interfaces sufficient or can I use tcpdump some how? Thanks for your patch!