Bug 441081 - No support for bonding or vlan tagging in iptraf
Summary: No support for bonding or vlan tagging in iptraf
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: iptraf
Version: 5.1
Hardware: All
OS: Linux
high
medium
Target Milestone: rc
: ---
Assignee: Nikola Pajkovsky
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On:
Blocks: 668957 719046
TreeView+ depends on / blocked
 
Reported: 2008-04-05 21:52 UTC by Javier de Miguel Rodríguez
Modified: 2018-11-14 16:59 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-04-24 19:41:58 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
src.rpm of iptraf (577.04 KB, application/x-rpm)
2008-05-07 08:17 UTC, Zdenek Prikryl
no flags Details

Description Javier de Miguel Rodríguez 2008-04-05 21:52:51 UTC
Description of problem:

Iptraf does NOT support bonding interfaces (bond0,bond1...) or vlan tagged
interfaces (eth0.4, bond0.5). 


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

iptraf shipped with rhel 5

How reproducible:

Configure bond intefaces or bond interface. Launch iptraf.

Steps to Reproduce:
1.
2.
3.
  
Actual results:



Expected results:


Additional info:

I do not know if this is a feature request or a bug: I think that iptraf is a
terrific tool but is useless in certain enterprise scenarios (bonding, vlan
tagging, etc).

Comment 1 Zdenek Prikryl 2008-05-07 08:17:05 UTC
Created attachment 304745 [details]
src.rpm of iptraf

Hello,
I tried to fix VLAN support and add BOND support. But I do not have access to a
real environment to test it. So, could you please build a package from src.rpm
in the attachment and test it? Thanks.

Comment 2 john.haxby@oracle.com 2010-01-13 16:12:44 UTC
In the absense of the original reporter confirming anything, I've tested this.

I can confirm that both vlan and bonded interface work.  If you have any specific tests you'd like run, please let me know.

Can we have this shipped with RHEL5 now please?

Comment 3 Nikola Pajkovsky 2010-01-13 16:26:25 UTC
I have to wait for pm_ack+ or rhel-5.6.0+. Maybe it will comes with next update.

Comment 4 RHEL Program Management 2010-01-13 16:29:31 UTC
This request was evaluated by Red Hat Product Management for
inclusion, but this component is not scheduled to be updated in
the current Red Hat Enterprise Linux release. If you would like
this request to be reviewed for the next minor release, ask your
support representative to set the next rhel-x.y flag to "?".

Comment 8 RHEL Program Management 2010-08-09 18:18:55 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 unfortunately unable to address this
request at this time. Red Hat invites you to ask your support
representative to propose this request, if appropriate and relevant,
in the next release of Red Hat Enterprise Linux.

Comment 9 Wolfram Schlich (LVM) 2010-09-30 11:22:06 UTC
iptraf does also not support bridge interfaces like br* and xenbr*.
will ask our TAM to push this.

Comment 15 RHEL Program Management 2011-05-31 14:09:55 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 unfortunately unable to address this
request at this time. Red Hat invites you to ask your support
representative to propose this request, if appropriate and relevant,
in the next release of Red Hat Enterprise Linux.

Comment 18 Larry Troan 2012-04-24 19:41:58 UTC
Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. 

Unfortunately, future updates of Red Hat Enterprise Linux 5 will have limited new features. Red Hat has reviewed this request and does not plan to consider implementing it at this point in the RHEL5 development cycle. I'm therefore closing this request as WONTFIX for RHEL5.

If you wish this request to be considered for RHEL6 or RHEL7, please reopen or clone this request against one or both of those releases.

Comment 19 Nikola Pajkovsky 2012-04-25 08:10:50 UTC
I'm going to build iptraf-ng for rhel5 in epel and all should be working out of the box.


Note You need to log in before you can comment on or make changes to this bug.