Closed TheCableGuy99 closed 10 months ago
Have you checked /usr/share/arp-scan/ ?
What happens when you run the command sudo get-oui -v
on your Pi.Alert host?
Hey,
I checked that directory and it's got similar files but not the exact one it's looking for:
total 2208
drwxr-xr-x 3 root root 4096 Nov 2 23:11 .
drwxr-xr-x 118 root root 4096 Nov 2 23:10 ..
drwxr-xr-x 2 root root 4096 Jul 5 09:20 2_backup
-rw-r--r-- 1 root root 140454 Oct 30 03:00 ieee-iab.txt.bak
-rw-r--r-- 1 root root 1049138 Nov 2 23:11 ieee-oui.txt
-rw-r--r-- 1 root root 1047891 Oct 30 03:00 ieee-oui.txt.bak
-rw-r--r-- 1 root root 2032 Feb 10 2021 mac-vendor.txt```
Output from the command:
```root@pialert:/usr/share/arp-scan# sudo get-oui -v
Renaming ieee-oui.txt to ieee-oui.txt.bak
Fetching OUI data from file://var/lib/ieee-data/oui.txt
Fetched 5606330 bytes
Opening output file ieee-oui.txt
34575 OUI entries written to file ieee-oui.txt```
Thanks.
I get the impression your reply is supposed to have opened my eye to the problem but I'm still not sure how to resolve this?
Please rename the file "ieee-iab.txt.bak" in the directory to "ieee-iab.txt".
The warning should then disappear. The vendor update script does not actually touch this file any more.
With my question I actually wanted to ask whether incorrect permissions could play a role
Worked like a charm, thank you mate :)
Hi,
I ran a manual scan from the cli and noticed several notifications of this error, should I be concerned or can it be ignored?