[network_checks] routing
Several issues here related with routing, might split in different tasks if needed / if the work load ends up too much. Just recalling what's been said about routing:
- Current openvpn configs (client/server combo) trigger an error with the route command (route command failed with error 7 I believe). However, that error puzzles me since the routes are correctly changed. Investigate this and try to get rid of that error.
- I think it would be good to have some route checking functions in LeapNetworkChecker: ** get routes from system ** get routes from openvpn (the tun0 gateway is showed in the debug panel) ** traceroute (to some well known, always up server? privacy implications, i.e., fingerprinting?) and get 1st hop. Check if that matches expected route. ** Have a function (might be that mtr alike one?) that can be triggered by a timer (or some smarter observer pattern) and is able to report when we cannot reach gateway / when routes are changed.
- what if there is already a non-standard default route? like if there is already a vpn running.
- what happens when connection can't route traffic?
(from redmine: created on 2012-09-14, closed on 2012-10-08)