On 05/22/2017 10:06 AM, jdd(a)dodin.org wrote:
Le 22/05/2017 à 15:47, James Knott a écrit :
On 05/22/2017 04:25 AM, jdd(a)dodin.org wrote:
I didn't understand how to add several
default routes with yast, but
You can only have one default gateway. What you're trying to do is set
up a specific route to that one site. The default gateway is the "last
resort", when no other route matches. In most cases, no other routes
are specified, but you are creating one that will be used ahead of the
the doc here
Seems pretty good. in "126.96.36.199 Configuring Routing", it is said one
can enter several default routes. I tested it's possible to do, but I
don't care now to validate the config (I don't want to break a working
system), so may be yast may not validate it
It says you can enter multiple routes, not multiple default routes.
There can only be one default route and that gets used only if there
isn't another match for the destination. With most computers, there
usually is not any other specified route. What that article mentions
about multiple default routes is:
"If more default routes are used, it is possible to specify the metric
option to determine which route has a higher priority. To specify the
metric option, enter |- metric /number/| in Options. The route with the
highest metric is used as default."
The metric is what determines which interface will be the default. The
one with the highest priority will be the one used. Incidentally, I
believe they got priority and metric mixed. In every example I've ever
seen, including routing protocols such as RIP, OSPF, EIGRP etc., the
metric is usually referred to as "cost", with the lower the better.
Lower metric = higher priority. In my message yesterday, I provided the
info for my notebook computer, which listed the WiFi metric at 600 and
Ethernet at 100. Ethernet has the lowest metric or cost and is used
when both Ethernet and WiFi are connected. I have verified this with
Wireshark. I could see that even when I tried to connect to the WiFi
address, the packets went through the Ethernet port.
if I correctly understand it it may have two use: if "metrics" is
used, but the doc states that the kernel is not using the metrics, or
in case one of the two links is out (cord plugged out, for example).
When I run route -n, after disconnecting the Ethernet cable, WiFi is
still shown with a metric of 600, but Ethernet is no longer listed. I
use network manager on my notebook. On my desktop, with static
configuration, the Ethernet metric is 0.
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse+owner(a)opensuse.org