Bug 7926 - arping: wrong interface name in error messages
Summary: arping: wrong interface name in error messages
Status: RESOLVED FIXED
Alias: None
Product: Busybox
Classification: Unclassified
Component: Networking (show other bugs)
Version: unspecified
Hardware: All All
: P5 minor
Target Milestone: ---
Assignee: unassigned
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-03-12 05:57 UTC by Alexander Korolkov
Modified: 2015-03-12 12:07 UTC (History)
1 user (show)

See Also:
Host:
Target:
Build:

Attachments
Fix error messages in arping (751 bytes, patch)
2015-03-12 06:00 UTC, Alexander Korolkov 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
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!