Bug 699178 - iptraf doesn't support the new naming scheme for network interfaces
Summary: iptraf doesn't support the new naming scheme for network interfaces
Keywords:
Status: CLOSED DUPLICATE of bug 682348
Alias: None
Product: Fedora
Classification: Fedora
Component: iptraf
Version: 15
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Nikola Pajkovsky
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-23 23:16 UTC by Raul Gutierrez S.
Modified: 2014-02-02 22:15 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2011-06-01 10:40:12 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Add support for new naming scheme on network interfaces. (659 bytes, patch)
2011-04-23 23:16 UTC, Raul Gutierrez S.
no flags Details | Diff

Description Raul Gutierrez S. 2011-04-23 23:16:11 UTC
Created attachment 494470 [details]
Add support for new naming scheme on network interfaces.

Description of problem:

Iptraf can't see interfaces named with the new naming scheme introduced by 2.6.38 (i.e.: em1, pci1, etc). 

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

How reproducible:
always.

Steps to Reproduce:
1. start iptraf (running kernel 2.6.38 or later with an embedded or pci network card)
2. go to `Detailed interface statistics`

  
Actual results:
You won't be able to see your network card

Expected results:
You should get em1 or pci1. 

Additional info:
I am attaching a patch that adds em and pci to the list of recognized interfaces (which is parsed by iptraf from /proc/net/dev).

Comment 1 Nikola Pajkovsky 2011-06-01 10:40:12 UTC
Thanks for patch, but I not going to apply the patch, because it's not a solution for everybody. I'm going to get rid of the white list of supported devices.

See the status of the duplicate bug

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


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