On 05/20/2017 02:41 PM, James Knott wrote:

One thing openSUSE does is assign a metric or "cost" to each route. If you do ifconfig, you'll see the WiFi connection has a higher metric than Ethernet. This means it's considered the lowest cost and therefore preferred. To force WiFi, you'll have to change the metrics, so that WiFi appears cheaper to use.

Ooopppsss!!! Ethernet has the lower cost and is preferred. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 05/20/2017 06:46 PM, John Andersen wrote:

Is it possible to set them dynamically under user (or at least root) control?

You can set the metric with the ifconfig command.

How does on establish multi-homed systems if the kernel ignores anything except the metric?

I don't think you have a coherent question there. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Le 21/05/2017 à 08:10, Andrei Borzenkov a écrit :

20.05.2017 21:21, jdd@dodin.org пишет:

...

Hello,

It happens that I have today two internet boxes. My main computer is connected to the two ones (one by ethernet, the other by wifi)

I use mostly the wifi only to connect to the box itself by IP (internal network), but sometime, for administrative purpose, I need to access internet by the second (wifi) box - mainly when I need to connect to the provider network.

How can I instruct firefox to use the wifi network when necessary? is it possible to give route infos in the url?

Is your system permanently connected to WiFi or you connect it only on demand?

it's permanent, and the default gateway is set to the ethernet network (fiber glass :-), I don't see why any metric should go, apart at config time. I noticed my problem because yesterday the "wifi" provider (the one that is on the wifi side - Free is it's name) experimented a day long outage. I could without problem use my ordinary route to connect to the net with the other provider, but when I wanted to subscribe to the web site Free use to the outage metrics, it refused me because I didn't come from it's own network. So I have to got to internet by the other one to subscribe. Of course, I can stop the ethernet network and set the gateway to the Free/wifi one for a moment, or change the route, but what I hoped for was a syntax to say "this url have to be reached through this route, not the other". I don't know how to phrase this short enough for a google search :-( I tried this right now: add a route through yast to 62.210.204.211, the IP of the server I want to reach, but firefox don't get there (connection fails, so it seems to try the new route) # route -n Table de routage IP du noyau Destination Passerelle Genmask Indic Metric Ref Use Iface 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth0 62.210.204.211 192.168.0.55 255.255.255.255 UGH 0 0 0 wlan0 192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 wlan0 192.168.0.254 192.168.0.55 255.255.255.255 UGH 0 0 0 wlan0 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 traceroute find it: linux-w4v5:/home/jdd # traceroute free-reseau.fr traceroute to free-reseau.fr (62.210.204.211), 30 hops max, 60 byte packets 1 linux-w4v5 (192.168.0.55) 2996.738 ms !H 2996.674 ms !H 2996.659 ms !H but not a browser: linux-w4v5:/home/jdd # w3m free-reseau.fr w3m: Can't load free-reseau.fr. what do I miss? thanks jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Le 21/05/2017 à 19:31, Andrei Borzenkov a écrit :

ip route get 62.210.204.211

# ip route get 62.210.204.211 62.210.204.211 dev wlan0 src 192.168.0.55 cache thanks jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Le 21/05/2017 à 21:56, Andrei Borzenkov a écrit :

21.05.2017 21:08, jdd@dodin.org пишет:

...

Le 21/05/2017 à 19:31, Andrei Borzenkov a écrit :

...

ip route get 62.210.204.211

# ip route get 62.210.204.211 62.210.204.211 dev wlan0 src 192.168.0.55 cache

That does not look right. According to this output 62.210.204.211 is directly accessible on device wlan0 which most likely is not true.

what do you mean by "directly"? my goal is to access it through this wlan

Please show output of

ip addr ip route

linux-w4v5:/home/jdd # ip addr 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 brd 127.255.255.255 scope host tentative lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 40:61:86:f7:58:c5 brd ff:ff:ff:ff:ff:ff inet 192.168.1.47/24 brd 192.168.1.255 scope global eth0 valid_lft forever preferred_lft forever inet6 fe80::4261:86ff:fef7:58c5/64 scope link valid_lft forever preferred_lft forever 3: wlan0: mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 70:f1:a1:a0:81:88 brd ff:ff:ff:ff:ff:ff inet 192.168.0.55/24 brd 192.168.0.255 scope global wlan0 valid_lft forever preferred_lft forever inet6 2a01:e35:2e45:75d0:291a:be03:8a46:c5cb/64 scope global temporary dynamic valid_lft 85995sec preferred_lft 39678sec inet6 2a01:e35:2e45:75d0:72f1:a1ff:fea0:8188/64 scope global mngtmpaddr dynamic valid_lft 85995sec preferred_lft 85995sec inet6 fe80::72f1:a1ff:fea0:8188/64 scope link valid_lft forever preferred_lft forever linux-w4v5:/home/jdd # ip route default via 192.168.1.1 dev eth0 proto dhcp 62.210.204.211 via 192.168.0.55 dev wlan0 192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.55 192.168.0.254 via 192.168.0.55 dev wlan0 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.47 thanks jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

21.05.2017 23:02, jdd@dodin.org пишет:

Le 21/05/2017 à 21:56, Andrei Borzenkov a écrit :

...

21.05.2017 21:08, jdd@dodin.org пишет:

...

Le 21/05/2017 à 19:31, Andrei Borzenkov a écrit :

...

ip route get 62.210.204.211

# ip route get 62.210.204.211 62.210.204.211 dev wlan0 src 192.168.0.55 cache

That does not look right. According to this output 62.210.204.211 is directly accessible on device wlan0 which most likely is not true.

what do you mean by "directly"?

Connected to the same broadcast domain as wlan0. ...

3: wlan0: mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 70:f1:a1:a0:81:88 brd ff:ff:ff:ff:ff:ff inet 192.168.0.55/24 brd 192.168.0.255 scope global wlan0 valid_lft forever preferred_lft forever ... default via 192.168.1.1 dev eth0 proto dhcp> 62.210.204.211 via 192.168.0.55 dev wlan0

This is wrong. To be able to talk to the outside world via wlan0 you should have gateway on this network, just like you have 192.168.1.1 on 192.168.1.0/24. You route should point to this gateway. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Le 22/05/2017 à 09:39, jdd@dodin.org a écrit :

how can I do that only for a domain/IP?

with some luck I may have found a solution... Starting here: https://doc.opensuse.org/documentation/leap/reference/html/book.opensuse.ref... "13.4.1.5 Configuring Routing" I didn't understand how to add several default routes with yast, but * removing the "dhcp automatic add gateway" on general network options tab * going to "route" tab, adding 62.210.204.211, 192.168.0.254 gateway and wlan0 * adding 192.168.1.1 (my eth0 gateway) eth0 as default gateway seems to give what I need # route -n Table de routage IP du noyau Destination Passerelle Genmask Indic Metric Ref Use Iface 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth0 62.210.204.211 192.168.0.254 255.255.255.255 UGH 0 0 0 wlan0 192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 wlan0 192.168.0.254 0.0.0.0 255.255.255.255 UH 0 0 0 wlan0 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 random web: # traceroute opensuse.org traceroute to opensuse.org (130.57.5.70), 30 hops max, 60 byte packets 1 192.168.1.1 (192.168.1.1) 0.338 ms 0.426 ms 0.625 ms 2 31tls2-nro-2.nro.gaoland.net (109.24.76.82) 5.673 ms 5.711 ms 5.742 ms (...) my special IP: # traceroute free-reseau.fr traceroute to free-reseau.fr (62.210.204.211), 30 hops max, 60 byte packets 1 192.168.0.254 (192.168.0.254) 2.642 ms 2.906 ms 3.246 ms 2 * * * 3 * * * and I can reach the page with firefox thanks jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Monday, 22 May 2017 17:55:10 ACST jdd@dodin.org wrote:

Le 22/05/2017 à 09:39, jdd@dodin.org a écrit :

...

how can I do that only for a domain/IP?

with some luck I may have found a solution...

Starting here:

https://doc.opensuse.org/documentation/leap/reference/html/book.opensuse.ref erence/cha.basicnet.html

"13.4.1.5 Configuring Routing"

I didn't understand how to add several default routes with yast, but

* removing the "dhcp automatic add gateway" on general network options tab * going to "route" tab, adding 62.210.204.211, 192.168.0.254 gateway and wlan0

* adding 192.168.1.1 (my eth0 gateway) eth0 as default gateway

seems to give what I need

Yes - that is exactly what you needed to do - you've now set a specific route to that one IP address via the wlan0 interface.

# route -n Table de routage IP du noyau Destination Passerelle Genmask Indic Metric Ref Use Iface 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth0 62.210.204.211 192.168.0.254 255.255.255.255 UGH 0 0 0 wlan0 192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 wlan0 192.168.0.254 0.0.0.0 255.255.255.255 UH 0 0 0 wlan0 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0

random web:

# traceroute opensuse.org traceroute to opensuse.org (130.57.5.70), 30 hops max, 60 byte packets 1 192.168.1.1 (192.168.1.1) 0.338 ms 0.426 ms 0.625 ms 2 31tls2-nro-2.nro.gaoland.net (109.24.76.82) 5.673 ms 5.711 ms 5.742 ms (...)

my special IP:

# traceroute free-reseau.fr traceroute to free-reseau.fr (62.210.204.211), 30 hops max, 60 byte packets 1 192.168.0.254 (192.168.0.254) 2.642 ms 2.906 ms 3.246 ms 2 * * * 3 * * *

And that shows that it works as expected. :)

and I can reach the page with firefox

thanks jdd

YW. Glad you got is sorted. :) -- ============================================================== Rodney Baker VK5ZTV rodney.baker@iinet.net.au ============================================================== -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Le 22/05/2017 à 15:47, James Knott a écrit :

On 05/22/2017 04:25 AM, jdd@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 default.

yes. the doc here https://doc.opensuse.org/documentation/leap/reference/html/book.opensuse.ref... Seems pretty good. in "3.4.1.5 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 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). I guess several routes mean also several gateways thanks jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 05/22/2017 10:28 AM, James Knott wrote:

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.

Here's what "ip route show" reveals: "> ip route show default via 172.16.1.1 dev eth0 proto static metric 100 default via 172.16.1.1 dev wlan0 proto static metric 600 172.16.1.0/24 dev eth0 proto kernel scope link src 172.16.1.42 metric 100 172.16.1.0/24 dev wlan0 proto kernel scope link src 172.16.1.40 metric 600" At the moment, the default route is via eth0, as it has the lower metric. When I disconnect the Ethernet cable, I get: "> ip route show default via 172.16.1.1 dev wlan0 proto static metric 600 172.16.1.0/24 dev wlan0 proto kernel scope link src 172.16.1.40 metric 600" And now my default route is via WiFi, the only route available. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 05/22/2017 10:50 AM, John Andersen wrote:

On 05/22/2017 07:28 AM, James Knott wrote:

...

The route with the highest metric is used as default." Lower metric = higher priority. Exactly. A constant source of confusion, and something that must have been the product of a non-english original writing.

The concept of COST based routing is probably obsolete, unless the definition of cost becomes very flexible and includes a wide variety of things.

I think cost is still a good analogy. In RIP, it was simply the number of hops, without regard to bandwidth. This meant that a low bandwidth, single hop route was considered better than a high bandwidth, multi-hop route. With OSPF, EIGRP and other more modern routing protocols, other factors such as bandwidth, delay, load and more may be considered. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 05/22/2017 10:28 AM, James Knott wrote:

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. I've noticed something else wrong. In the section on IPv6, the book mentions site local addresses. They have been deprecated for years, in favour of unique local addresses.

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org