Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Cause:
tcpdump was treating argument for -i option as a number if it had numeric prefix.
Consequence:
Packet capturing wasn't started at all on specified interface or it could get started on wrong interface.
Fix:
Treat the argument to -i options as a number if it's *all*
number. Thus interface names such as 192_1_2 aren't treated as interface number 192.
Result:
tcpdump should start correctly on specified interface even if interface name has numeric prefix.
Description of problem:
tcpdump on interface which name starts as number.
# tcpdump -n -i 102a9f7e2f -c 100 stp
tcpdump: Invalid adapter index
Version-Release number of selected component (if applicable):
4.0.0-3.20090921gitdf3cb4
How reproducible:
Run tcpdump on interface which name starts as number.
For example: # tcpdump -n -i 102a9f7e2f -c 100 stp
Steps to Reproduce:
1.
2.
3.
Actual results:
tcpdump: Invalid adapter index
Expected results:
Additional info:
Comment 4RHEL Program Management
2013-10-13 23:29:54 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.
Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.
tcpdump 4.3 and later use strtol() in that fashion; what version of tcpdump is in RHEL 6? Is this bug really requesting that the change made in tcpdump 4.3 be backported to an older version of tcpdump?
If everything goes as planned then tcpdump will be rebased in next version of RHEL and this bug should be fixed by rebase. Anyway, Guy thank you very much for taking the time to look at this, very appreciated.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://rhn.redhat.com/errata/RHBA-2015-1294.html