Red Hat Bugzilla – Bug 682337
assumes all network devices are named ethX or trX
Last modified: 2014-03-16 23:26:41 EDT
Created attachment 482379 [details]
Patch... just read all devices with proper addresses
Description of problem:
Network devices can have arbitrary names, and due to http://fedoraproject.org/wiki/Features/ConsistentNetworkDeviceNaming, will have different names in Fedora 15.
amtu assumes all devices are ethX or trX.
Version-Release number of selected component (if applicable):
Via source code inspection
Not sure this patch is adequate. The system could have tunnels and bridges and other things that amtu should not touch. How do you identify just ethernet and tokenring interfaces in the new naming scheme?
What is amtu verifying about the adapter that makes a bridge or bonded adapter invalid?
The code is just to check that the basic security assumptions are met, meaning you have lossless IO. There is a programming note that the test does not work for async network devices. So, I think the code looks for ethernet and tokenring knowing they are not async.
Probably keying off of the header type (/sys/class/net/<device>/type, see include/linux/if_arp.h for the list) is best then?