Den 2018-04-04 kl. 15:45, skrev Carlos E. R.:
On 2018-04-04 15:22, Michael Ströder wrote:
Carlos E. R. wrote:
On the Linux side I configured for the same IP, but on Windows I have not bothered because I use it rarely (and after all, I can not ssh-in to Windows). It might be a problem for Samba, though: I have to open ports on the Linux firewall for two different IPs for the same machine.
I wonder why you argue with the Windows behaviour if you don't have the very same requirements with this OS.
No, but the question arose about how Windows behaved in this situation.
BTW: I think what you want is best achieved by connecting your (IP-less) eth0 and wlan0 to a bridge interface and assign the IP to that.
Sorry, I don't understand.
You create a software bridge between eth0 and wlan0 and that the bridge has it's own IP configuration. Like so: ip link add name br0 type bridge ip link set dev br0 up ip link set dev wlan0 master br0 ip link set dev eth0 master br0 ip address add 10.0.0.1/24 dev br0 You can manipulate STP for the different switch ports. I only do this with "normal" ethernet in our linux-routers so I'm not really sure about the bridging of 802.11 and 802.3 with iputils bridge. There is however other bridges you could use. NM has integration to Openvswitch which might be up your alley as you said you use NM for this.
What I do, and works, is having the same IP on both eth0 and wlan0 interfaces. I "only" have to remember to disable wlan when I insert the cable.
Now, Michal Kubecek has posted a suggestion that I want to try, using STARTMODE='ifplugd' and adjusting priorities.
-- /bengan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org