vpnc-0.3.2 fails to set default route due to a bug in vpnc-connect vpnc-connect reads ouptut of /sbin/ip command and then after "fixing" it feeds it back to the /sbin/ip unfortunatey the "fixing" went wrong and /sbin/ip could not accept the given parameters Reproducible: Always Steps to Reproduce: 1. set up the network interface 2. start vpnc-connect Actual Results: an error message appears from /sbin/ip route -n does not contain the default route it should (including gateway address) Expected Results: no error messages proprly working routing after correcting fix_ip_get_output() function within vpnc-connect to the form cited below: fix_ip_get_output () { sed 's/cache//;s/metric \+[0-9]\+ [0-9]\+//g' | xargs echo } it works again...
Paul, do you know if vpnc-0.3.3 fixes this problem?
Forget the question. I have two new ones: - Is this still an issue? - What's your iproute2 version? - What's the output of `ip route get $YOURGATEWAY`?
1/ it is not an issue as long as I have fix_ip_get_output () { sed 's/cache//;s/metric \+[0-9]\+ [0-9]\+//g' | xargs echo } in my ebuild... 2/ sys-apps/iproute2-2.6.11.20050330 3/ # ip route get XXX.XXX.XXX.XXX XXX.XXX.XXX.XXX dev ath0 src XXX.XXX.XXX.YYY cache mtu 1500 advmss 1460 metric 10 64
This is still an issue in vpnc-0.3.3, the fix mentioned here works for me. sys-apps/iproute2-2.6.11.20050330-r1
fixed in vpnc-0.3.3 ebuild