Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#40947 - [nmap] use internal libpcal
Attached to Project:
Arch Linux
Opened by ValdikSS (ValdikSS) - Monday, 23 June 2014, 12:18 GMT
Last edited by Gaetan Bisson (vesath) - Sunday, 17 August 2014, 03:09 GMT
Opened by ValdikSS (ValdikSS) - Monday, 23 June 2014, 12:18 GMT
Last edited by Gaetan Bisson (vesath) - Sunday, 17 August 2014, 03:09 GMT
|
DetailsDescription:
It seems like nmap have some kind of incompatibility with newer versions of libpcap. Some scripts don't work as expected. Recompiling with --with-libpcap=included fixes all the problems. Steps to reproduce: sudo nmap -sn your_gateway_ip --script ip-forwarding --script-args='target=8.8.8.8' Expected result: Host script results: | ip-forwarding: |_ The host has ip forwarding enabled, tried ping against (8.8.8.8) Actual result: None |
This task depends upon
Closed by Gaetan Bisson (vesath)
Sunday, 17 August 2014, 03:09 GMT
Reason for closing: Fixed
Additional comments about closing: nmap-6.46-2 in [extra]
Sunday, 17 August 2014, 03:09 GMT
Reason for closing: Fixed
Additional comments about closing: nmap-6.46-2 in [extra]
Okay, I'll build against the included libpacp until we can avoid it.