RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 963927 - arping is not compatible with network namespaces
Summary: arping is not compatible with network namespaces
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: iputils
Version: 6.4
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: 6.5
Assignee: Jan Synacek
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks: 880142 883504 968342 971672
TreeView+ depends on / blocked
 
Reported: 2013-05-16 19:14 UTC by Maru Newby
Modified: 2016-04-26 13:53 UTC (History)
13 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-11-14 10:37:08 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
workaround patch (615 bytes, patch)
2013-05-16 22:54 UTC, Thomas Graf 		no flags Details | Diff
[Patch] fall back when sysfs broadcast file is not readable (1.10 KB, patch)
2013-05-22 07:10 UTC, Jan Synacek 		no flags Details | Diff
Show Obsolete (1) View All

Description Maru Newby 2013-05-16 19:14:52 UTC 
Description of problem:

Attempting to invoke arping in a network namespace (presuming a netns-supporting kernel and iproute2 have been ocnfigured) does not work.


Version-Release number of selected component (if applicable):


How reproducible:

Consistent.


Steps to Reproduce:

1. Install a netns-supporting kernel/kernel-firmware/iproute.
2. Add a namespace: ip netns add namespace1
3. Add a veth pair: ip link add v0 type veth peer name v1 netns namespace1
4. Bring the netns device up: ip netns namespace1 exec ip link set v1 up
5: Invoke arping in the namespace on any ip: ip netns namespace1 arping -A -U -I v1 192.168.1.1

  
Actual results:

Stderr: 'sysfs read broadcast value: No such file or directory'


Expected results:

ARPING 192.168.1.1 from 192.168.1.1 veth0
Sent 3 probes (3 broadcast(s))
Received 0 response(s)


Additional info:
Comment 3 Thomas Graf 2013-05-16 22:54:27 UTC 
Created attachment 749104 [details]
workaround patch

The background for this is that the netns backport for 6.5 is not complete and does not include the sysfs bits. This leads to the /sys/class/net/$DEV/ directory not being available in the non default netns. arping reads its broadcast address via sysfs.

The following workaround has been used successfully in combination with the netns backport and RHOS. It's a POC patch that should be converted into a fallback alternative if the sysfs broadcast file is not available, i.e. fall back to using a default broadcast address of '-1' if the broadcast address can't be read.

Alternatively the broadcast address could be read from a source other than sysfs, e.f. by parsing the output of 'ip link' or by issueing a netlink request which are both netns aware.
Comment 5 Jan Synacek 2013-05-21 07:52:42 UTC 
Thomas, is there a possibility that the broadcast address could be anything else than all 0xff's? I'm not aware that it happens, so I think that the workaround patch is ok to apply, *as long as it gets removed once the netns backport is completed*.
Comment 6 Thomas Graf 2013-05-21 11:04:59 UTC 
(In reply to Jan Synacek from comment #5)
> Thomas, is there a possibility that the broadcast address could be anything
> else than all 0xff's? I'm not aware that it happens, so I think that the
> workaround patch is ok to apply, *as long as it gets removed once the netns
> backport is completed*.

It could differ but only in very rare situations. What seems to be the best option forward is to fall back to all 0xff's if the sysfs file cannot be read.
Comment 7 Jan Synacek 2013-05-21 11:07:46 UTC 
I agree. I'll write a patch doing exactly that.
Comment 8 Jan Synacek 2013-05-21 11:15:37 UTC 
I'm setting the old needinfo flags that should have stayed there back.
Comment 10 Jan Synacek 2013-05-22 07:10:11 UTC 
Created attachment 751541 [details]
[Patch] fall back when sysfs broadcast file is not readable
Note You need to log in before you can comment on or make changes to this bug.