I found this in f12 and tried posting this bug to the kernel netdev list http://marc.info/?l=linux-netdev&m=126823674823150 but got no reply. Maybe it's just a cosmetic issue in iproute2? It's still in f13 and pretty easy to reproduce: # ip route add 10.0.0.0/8 via 192.0.2.1 metric $[2**31] # ip route show 10.0.0.0/8 10.0.0.0/8 via 192.0.2.1 dev eth4 metric -2147483648 Something is wrong somewhere with signedness. The highest metric that will display properly is one less: # ip route add 10.0.0.0/8 via 192.0.2.1 metric $[2**31-1] # ip route show 10.0.0.0/8 10.0.0.0/8 via 192.0.2.1 dev eth4 metric 2147483647 Are metrics with the 32nd bit set legit? Or should the tool prevent it like this: # ip route add 10.0.0.0/8 via 192.0.2.1 metric $[2**32] Error: argument "4294967296" is wrong: "metric" value is invalid Please forward to upstream contact if appropriate. Thanks!
Created attachment 442167 [details] Print route metric as unsigned int This really seems to be a cosmetic issue. Does the attached patch solve it for you? Koji builds for testings: http://koji.fedoraproject.org/koji/taskinfo?taskID=2437127
I suppose the printf patch solves the issue.
iproute-2.6.33-4.fc13 has been submitted as an update for Fedora 13. https://admin.fedoraproject.org/updates/iproute-2.6.33-4.fc13
iproute-2.6.35-3.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/iproute-2.6.35-3.fc14
iproute-2.6.35-3.fc14 has been pushed to the Fedora 14 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update iproute'. You can provide feedback for this update here: https://admin.fedoraproject.org/updates/iproute-2.6.35-3.fc14
iproute-2.6.35-3.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.
iproute-2.6.33-4.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.