On 04/01/2017 04:24 PM, David C. Rankin wrote:
Yes, this is a PITA. There is supposed to be a rate prioritization routine that runs to always provide a route via the fastest connection. My experience is that it just confuses the sh.. out of whatever is supposed to provide the default route, and network traffic comes to a screeching halt.
Indeed. I seem to recall this had something to do with the "metric" parameter. While refreshing my memory on the meaning of the "metric" column in the following:
jsa@poulsbo:~> ip r default via 192.168.2.1 dev eth0 proto static metric 100 default via 192.168.86.1 dev wlan0 proto static metric 600 192.168.2.0/24 dev eth0 proto kernel scope link src 192.168.2.232 metric 100 192.168.86.0/24 dev wlan0 proto kernel scope link src 192.168.86.232 metric 600 192.168.193.0/24 dev vmnet8 proto kernel scope link src 192.168.193.1
...I came across an oblique reference to the fact that modern kernels seem to pay that value no heed any more. See https://www.cyberciti.biz/faq/what-is-a-routing-table/ -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org