Hello, > Here is the output of : route -n : > > 0.0.0.0 192.168.50.2 0.0.0.0 UG 0 0 > 0 eth0 > 169.254.0.0 0.0.0.0 255.255.0.0 U 1002 0 > 0 eth0 > 172.16.2.6 192.168.50.184 255.255.255.255 UGH 0 0 0 > eth0 > 192.168.50.0 0.0.0.0 255.255.255.0 U 0 0 > 0 eth0 > > When I try to ping 172.16.2.6, it doesn't work while the first available > route is used (0.0.0.0 via 192.168.50.2)
That is strange indeed... > How can I modify the order of the route table to force use of the right > route ? You should not need to, and I also don't know how you would be able using route commands. However what is weird is that it actually does use the first entry. It *should* use the most specific entry. And you can not get more specific than 172.16.2.6/32. Have you tried to reach it after dropping (temporarily) your default gateway? Just to see that it is indeed correctly there and that gateway to 172.16.2.6 does function. -- Kind regards, André -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
