** Changed in: libpcap
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1457472
Title:
TPACKET_V3 in Linux before 3.19 causes packet loss in libpcap
Inspired by the flow-disruptor workaround, I did a proof-of-concept nmap
workaround as follows:
http://paste.ubuntu.com/23176851/
Obviously, this is nowhere near production-ready code, but I wanted to
convince myself that the pcap_set_immediate_mode() workaround could work
in nmap as well.
--
** Project changed: tcpdump => libpcap
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1457472
Title:
TPACKET_V3 in Linux before 3.19 causes packet loss in libpcap
Status in libpcap:
** Changed in: nmap
Status: Unknown => New
** Changed in: tcpdump
Status: Unknown => New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1457472
Title:
TPACKET_V3 in Linux
I have tested this on kernel 4.4.0 (in Xenial) and I don't think the fix
that went into 3.19 fixed the entire issue.
My understanding is that since nmap uses a relatively long pcap_select()
timeout, and the packet buffers in the kernel aren't filling up fast
enough, the packet loss can still be
** Tags added: cherry-pick kernel-fixed-upstream reverse-bisect-done
** Changed in: linux (Ubuntu)
Importance: Undecided = High
** Changed in: linux (Ubuntu)
Status: Confirmed = Triaged
--
You received this bug notification because you are a member of Kernel
Packages, which is
6 matches
Mail list logo
