arp-scan returns an empty scan

Bug #1849740 reported by zebul666
40
This bug affects 8 people
Affects Status Importance Assigned to Milestone
arp-scan (Debian)
Fix Released
Unknown
arp-scan (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

in 19.10, arp-scan (1.9.5) does not work as expected anymore.

It just returns an empty scan when run:

$ sudo arp-scan -I enp1s0 -l -r 3
Interface: enp1s0, datalink type: EN10MB (Ethernet)
Starting arp-scan 1.9.5 with 256 hosts (https://github.com/royhills/arp-scan)

24 packets received by filter, 0 packets dropped by kernel
Ending arp-scan 1.9.5: 256 hosts scanned in 3.235 seconds (79.13 hosts/sec). 0 responded

This is not expected. It was working fine in 19.04.

Moreover, compiling an running arp-scan from https://github.com/royhills/arp-scan works as expected:

$ sudo ./arp-scan -I enp1s0 -l
Interface: enp1s0, type: EN10MB, MAC: xx:xx:xx:xx:xx:xx, IPv4: 192.168.44.115
Starting arp-scan 1.9.6 with 256 hosts (https://github.com/royhills/arp-scan)
192.168.44.1 xx:xx:xx:xx:xx:xx YYYYY
192.168.44.55 xx:xx:xx:xx:xx:xx YYYY
192.168.44.106 xx:xx:xx:xx:xx:xx GGGG
192.168.44.117 xx:xx:xx:xx:xx:xx HHHH
192.168.44.121 xx:xx:xx:xx:xx:xx HJJJJJ
192.168.44.103 xx:xx:xx:xx:xx:xx GGHJJ
192.168.44.110 xx:xx:xx:xx:xx:xx HHHH
192.168.44.230 xx:xx:xx:xx:xx:xx JJJJ

8 packets received by filter, 0 packets dropped by kernel
Ending arp-scan 1.9.6: 256 hosts scanned in 2.105 seconds (121.62 hosts/sec). 8 responded

scan has been redacted

Please upgrade to 1.9.6 or even the upcoming 1.9.7 or apply any needed fix. thanks

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: arp-scan 1.9.5-1build1
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 24 23:55:06 2019
InstallationDate: Installed on 2018-05-07 (535 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SourcePackage: arp-scan
UpgradeStatus: Upgraded to eoan on 2019-10-23 (1 days ago)

Revision history for this message
zebul666 (zebul666) wrote :
Revision history for this message
Claudio (claudio-fischer) wrote :

I can confirm this bug in Ubuntu 19.10

Revision history for this message
fiver22 (fiver22) wrote :

I experienced this behaviour in Ubuntu 19.10 deriv. (Pop!_OS) -tried older .debs to no avail. built latest from github and is now working as expected.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in arp-scan (Ubuntu):
status: New → Confirmed
Changed in arp-scan (Debian):
status: Unknown → Fix Committed
Changed in arp-scan (Debian):
status: Fix Committed → Fix Released
Revision history for this message
VAP (shnushnu) wrote :

Any updates on a fix for Ubuntu?

I'm still encountering this issue on Ubuntu 19.10 using arp-scan 1.9.5.

Revision history for this message
Carroarmato0 (carroarmato0) wrote :

Still present, using nmap as a workaround for the time beeing: sudo nmap -sP -PR <network>

Revision history for this message
Esteban Richmond-Salazar (ersiq) wrote :

I confirm this bug in version 1.9.5

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.