On 2018-04-03 21:59, James Knott wrote:
On 04/03/2018 03:54 PM, Carlos E. R. wrote:
I never said use the same IP address for both interfaces. Only that Linux allows you to reach the WiFi address, even when connected via Ethernet.
But I do want both interfaces to have the same IP, and have only one active at a time. I want to do on another computer "ssh laptop" and be sure to reach it no matter if it is on WiFi or cable. I do not want to do "ssh laptop_eth" or "ssh laptop_wifi" depending.
That's the way it works here. No matter which address I use, when both connections are up, I can connect.
And how do you manage to do it automatically? On my "stable" partition, I have both eth0 and WiFi connections have the same IP and they collide, I get martians and failed connections. I have to disable one manually. I insist, I want to have both interfaces on the same address. The reason is to ssh from another machine and not having to think which interface it is using this time. The only way I know is to manually disconnect one.
When running Leap 15.0, different IP for each, different metrics, but same network - they connect to the same exact router, they are in the same segment - things work, except traceroute.
Make sure your firewall is turned off.
But I do want it on.
You can turn it off for testing.
But your way of expressing it meant to disable it permanently as a solution.
Anyway, I disabled the firewall on the laptop and still traceroute fails.
It is the firewall (SuSEfirewall, Leap 42.3) at the destination that is the culprit.
The firewall at the target is the problem. It will block traceroute.
That's what I said. -- Cheers/Saludos Carlos E. R. (testing openSUSE Leap 15.0, at Minas-Anor) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org