WARNING Daemon Daemon No route exists to 168.63.129.16

Hi,

Why this warning while the default route created by the DHCP client could be enough? I think that there is a possibility to improve your checks.

Suggestion: why not using the Linux command `ip route get 168.63.129.16` ? And parse it's output? (with the help of the shellutil.run_command() method?). Routing tables on a Linux machine could be complex (even more complex if the machine supports BGP, OSPF or other routing protocols).

All the Best,
A CacheGuard Developer

PS: we developed a subclass of the DefaultOSUtil for our OS. How can we submit our works?

Start by tracing the daemon's check that emits “No route exists to 168.63.129.16” and review how DefaultOSUtil and shellutil.run_command() are used. Compare the current warning with the result of `ip route get 168.63.129.16`; done means the route check handles valid default or complex routes without a false warning.

Written by the indexing model from the issue text.