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.
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.
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. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org