I think the issue is the the nm_system_apply_ip4_config () method always returns TRUE, ignoring any errors from nm_system_device_set_ip4_route (), which returns NULL to signify an error adding a route.
I've added a preliminary fix for this, by adding logic to check for NULL and immediately return FALSE. instead of continuing to iterate the through any remaining routes to be added. Note, this may need to be re-worked to ensure that route object references are all properly cleaned up, but it should suffice for testing the fix.
A version of this first attempt at patching can found in my PPA:
I think the issue is the the nm_system_ apply_ip4_ config () method always returns TRUE, ignoring any errors from nm_system_ device_ set_ip4_ route (), which returns NULL to signify an error adding a route.
I've added a preliminary fix for this, by adding logic to check for NULL and immediately return FALSE. instead of continuing to iterate the through any remaining routes to be added. Note, this may need to be re-worked to ensure that route object references are all properly cleaned up, but it should suffice for testing the fix.
A version of this first attempt at patching can found in my PPA:
https:/ /launchpad. net/~awe/ +archive/ ubuntu/ ppa
Note, as it's a FIX for RTM, it's the 0.9.8 version.