Bug 7926

Summary:	arping: wrong interface name in error messages
Product:	Busybox	Reporter:	Alexander Korolkov <alexander.korolkov>
Component:	Networking	Assignee:	unassigned
Status:	RESOLVED FIXED
Severity:	minor	CC:	busybox-cvs
Priority:	P5
Version:	unspecified
Target Milestone:	---
Hardware:	All
OS:	All
Host:		Target:
Build:
Attachments:	Fix error messages in arping

Description Alexander Korolkov 2015-03-12 05:57:46 UTC

In arping, all error messages start with "arping: interface eth0", even if another interface is used.

Example:

# ./busybox arping -I eth1 192.168.0.1
arping: interface eth0 not found: No such device

This is because error template is formed before parsing command line arguments, so it always uses default interface name "eth0". Attached patch fixes this bug.

Comment 1 Alexander Korolkov 2015-03-12 06:00:42 UTC

Created attachment 5921 [details]
Fix error messages in arping

Comment 2 Denys Vlasenko 2015-03-12 12:07:14 UTC

Fixed in git, thanks!