Description of problem: In draknetcenter, we can write the metrics of an interface in advanced. It writes in /etc/sysconfig/network-scripts/ifcfg-eth0 a line like METRIC=10 But the route command always shows METRIC=0 for all interfaces. It seems this parameter is not applied.
Seems to be working here on my i586 system ... # route|grep -e default -e Metric Destination Gateway Genmask Flags Metric Ref Use Iface default 192.168.10.1 0.0.0.0 UG 10 0 0 eth0
CC: (none) => davidwhodgins
I tried to apply manually : ifconfig eth0 metric 10 SIOCSIFMETRIC: Operation not supported As this is new hardware, maybe a driver limitation? Strange that both Ethernet and Wi-Fi have the problem : wl : Broadcom Corporation|BCM43224 802.11a/b/g/n [NETWORK_OTHER] (vendor:14e4 device:4353 subv:103c subd:1510) (rev: 01) e1000e : Intel Corporation|82577LC Gigabit Network Connection [NETWORK_ETHERNET] (vendor:8086 device:10eb subv:103c subd:1471) (rev: 05)
I'm facing similar problems. But I noticed that one can edit metrics manually with cmd ifmetric from pkg ifmetric.
CC: (none) => jani.valimaa
CC: (none) => mageia
Actually noticed that all this is caused by ifmetric failing sometimes. Added patch from Debian bugtracker [1] to ifmetric and it solves the problem, at least for me. Pushed new ifmetric version to core/updates_testing. Please test if ifmetric-0.3-9.1.mga1 solves the problem also for you. [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=514197#22
Problem solved with new ifmetric
Status: NEW => RESOLVEDResolution: (none) => FIXED
I'm reopening as this new ifmetric pkg should be pushed to core/updates too. However this may be a bit tricky to test and QA'ed as not every system is affected.. At least the new pkg has fixed the bug for me and the original poster.
Status: RESOLVED => REOPENEDResolution: FIXED => (none)Assignee: bugsquad => qa-bugs
I've tried to test this but the only way I'm able to alter the metric is via the Network Centre. ifmetric gives no error but has no affect ifconfig eth1 metric 10 gives SIOCSIFMETRIC: Operation not supported I don't think I am able to test this update. Can you say which architectures you both tested on please, we may be able to validate it that way if both i586 & x86_64 are covered.
CC: (none) => eeeemail
On my x86_64 I can confirm that before installing ifmetric adjusting the metric parameter in mcc had no effect. The metric remained '0' On installing ifmetric and stopping starting the interface, then the metric is correctly reported as that set in mcc. It appears to work as advertised.
CC: (none) => derekjenn
I've tested this with my i586 machine. I have also a x86_64 (cauldron) machine but can't remember if it was also affected. However, setting metrics with cmd 'ifmetrics eth0 22' as root works now in both machines. This can be confirmed with cmd 'route -n' afterwards.
Thankyou both. I think that as this is difficult to reproduce without affected systems and it has been shown to be an effective solution for both i586 and x86_64 it should be OK to validate. Advisory: ------------- This update corrects an issue with setting the metric of a network interface with some configurations. ------------- SRPM: ifmetric-0.3-9.1.mga1.src.rpm Could somebody from sysadmin please push this from core/updates_testing to core/updates. Thankyou!
Keywords: (none) => validated_updateCC: (none) => sysadmin-bugs
Hardware: x86_64 => All
update pushed.
Status: REOPENED => RESOLVEDCC: (none) => dmorganecResolution: (none) => FIXED