Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
For bugs related to Red Hat Enterprise Linux 4 product line. The current stable release is 4.9. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 180981

Summary: tcpdump -i ib0 not working with OpenIB IPoIb
Product: Red Hat Enterprise Linux 4 Reporter: Scott Weitzenkamp <sweitzen>
Component: tcpdumpAssignee: Martin Stransky <stransky>
Status: CLOSED DUPLICATE QA Contact: David Lawrence <dkl>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.3   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-02-10 22:30:20 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Scott Weitzenkamp 2006-02-10 22:28:34 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322)

Description of problem:
I am using 2.6.9-27 x86_64 and ia64 kernels, testing OpenIB.  IPoIB is working in general, but tcpdump does not work with IPoIB.

# tcpdump -i ib0
tcpdump: ioctl: Value too large for defined data type

strace says:

ioctl(3, SIOCGIFINDEX, {ifr_name="lo", ifr_index=1}) = 0
ioctl(3, SIOCGIFHWADDR, {ifr_name="ib0", ???}) = -1 EOVERFLOW (Value too large f
or defined data type)
close(3)                                = 0
write(2, "tcpdump: ", 9tcpdump: )                = 9
write(2, "ioctl: Value too large for defin"..., 44ioctl: Value too large for def
ined data type) = 44


Version-Release number of selected component (if applicable):
tcpdump-3.8.2-9.RHEL4

How reproducible:
Always

Steps to Reproduce:
1. modprobe ib_ipoib
2. tcpdump -i ib0
3.
  

Actual Results:  command failed

Expected Results:  packet dump

Additional info:

none

Comment 1 Scott Weitzenkamp 2006-02-10 22:30:20 UTC

*** This bug has been marked as a duplicate of 180980 ***