Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 524714 - net-libs/libpcap newer than 1.4.0 causes net-wireless/reaver-1.4-r1 to not work
Summary: net-libs/libpcap newer than 1.4.0 causes net-wireless/reaver-1.4-r1 to not work
Status: RESOLVED DUPLICATE of bug 524712
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Library (show other bugs)
Hardware: AMD64 Linux
: Normal normal (vote)
Assignee: Gentoo Linux bug wranglers
URL: https://code.google.com/p/reaver-wps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-10-07 18:05 UTC by Barvinok
Modified: 2014-10-07 18:07 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Barvinok 2014-10-07 18:05:11 UTC
wash utility which is a part of net-wireless/reaver dies silently instead of scanning nearby wifi spots. Developer of reaver-wps says this is because libpcap had changed some internals ( https://code.google.com/p/reaver-wps/issues/detail?id=591 ). There's no workaround provided nor fix available from the dev even though it's already 5 months since then. Supposedly the change was introduced with libpcap 1.5.x , whereas 1.4.x worked fine with reaver.
That wouldn't have been an issue had 1.4.x been still in the portage tree. But it is not. Consulted on IRC they said gentoo team could fix that.

Reproducible: Always

Steps to Reproduce:
1. Emerge net-libs/libpcap newer than 1.4.x
2. Emerge net-wireless/reaver
3. run /usr/bin/wash
Actual Results:  
wash utility did not work, dies quietly

Expected Results:  
wash should perform network scanning

As soon as I installed libpcap 1.3.0 everything worked. Probably 1.4.0 will also work. But of course I'd like to see a patch to reaver to make it understand the most recent libpcap out there.
Comment 1 Jeroen Roovers (RETIRED) gentoo-dev 2014-10-07 18:07:08 UTC

*** This bug has been marked as a duplicate of bug 524712 ***