overkill

OK, figured it out. Just use the ip route syntax in quotes in the /etc/conf.d/netif.eth0. Something like this - adjust ip's and interface as they pertain to your setup. route="0.0.0.0/0 via 192.168.1.28 dev eth0 metric 10" Should do the trick

You can/should control your routes by the metric. You can/should have your secondary default route added with a higher metric value than your default route. If the default route is inaccessible, it will use the next route for 0.0.0.0/0. When the gateway/cable modem becomes accessible once more, the default route is chosen since it's metric is lower. I'm sure that openrc can set this up when the network is brought up, I've just never looked for the way to do it. Now that I think about it, I know I read about this very topic in when I used Gentoo and it's version of openrc. Check the do

You're welcome. Glad you got it worked out.

I could live without it, but if I don't have too... AWESOME! Thanks dantrell!

I'll miss my transparent gnome-terminal shell windows :(

It is becoming more common to experience some sort of conflict/block/unmet dependency. Gentoo and Funtoo are diverging. Funtoo needs it's own portage tree, or at least some sort of sanity checking before letting Gentoo ebuilds destroy clean funtoo merges. Just my 2 cents worth.

I run a Wireless Internet Server Provider in rural Texas. Deal with wireless issues on a daily basis. Looks like interference or poor signal strength to me. Do you have neighbors close by?, running on the same or overlapping your channel?. I'd try switching channels and see if your packet loss improves. What your signal level and your noise level when you are experiencing packet loss? Are you far from your router? Try moving closer. Still have high latency/packet loss? When consumer grade wireless routers begin to die, they exhibit strange, inconsistent behavior. You could try