[opensuse-support] wifi and eth wicked same network should fallback - bond?
Hi, i try the whole day to get a laptop tumbleweed kde, xwindows, wicked running with wifi and cable lan, static ipv4 only. network is 192.168.0.x cable: enp3s0 should be 192.168.0.23 wifi: wlp2s0 should be 192.168.0.43 (driver is iwlwifi) most of time this laptop is connected to the eth0 sometimes if it is not connected, it should use wifi to go into the same network (and to go only in this network). so i decided to configure both networks inside yast i get it running with cable, and i get it running with wifi, BUT if i activate both together inside yast, it will mess up. the reason seems to be the routing. if i do NOT assign enp3s0 or wlp2s0 "-" inside yast, ip ro will show no routing at all. if insert one of them, it will partly work as long as this connection is ok. i tried to add a second routing with: ip route delete default ip route add default via 192.168.0.99 metric 101 dev wlp2s0 ip route add default via 192.168.0.99 metric 102 dev enp3s0 but still the same problem. then i was thinking try to bond both networkadapters together: in yast i made a bond0 gave theme the address 192.168.0.23 and put both network adapters to the bond0 (removed the ip addresses and they jump to "activate by hotplugged" and made standartroute to bond0 as soon as i say ok in yast it takes some seconds to write the configuration, and after this (if before both adapters where visible inside the network) the wifi adapter will switched off, never seen by ip ro (and of course also not inside the net) i checked also: rfkill list (to make shure its not blocked) all are on "no" inside /etc/sysconfig/network/ifcfg-bon0 both slaves are inside, and the ifcfg-wlp2s0 file only differs from standalone to the bond version in BOOTPROTO and STARTMODE and as i have read inside internet, thats correct. could anybody help me to get it running like: fallback from one to the other network adapters, normally using enp3s0 if not present using wlp2s0 i do not take care how to get to this. i have had it running with opensuse 42.2? i think was before on that laptop. as i remember there it was networkmanager. but if i now switch inside yast to networkmanager, i have no possibility to change anything inside yast at enp3s0 or bond0 or wlp2s0 and network is not present at all. simoN -- www.becherer.de -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On 30/09/2018 15.34, Simon Becherer wrote:
Hi,
i try the whole day to get a laptop tumbleweed kde, xwindows, wicked running with wifi and cable lan, static ipv4 only. network is 192.168.0.x cable: enp3s0 should be 192.168.0.23 wifi: wlp2s0 should be 192.168.0.43 (driver is iwlwifi)
most of time this laptop is connected to the eth0 sometimes if it is not connected, it should use wifi to go into the same network (and to go only in this network).
so i decided to configure both networks inside yast
i get it running with cable, and i get it running with wifi, BUT if i activate both together inside yast, it will mess up. the reason seems to be the routing. if i do NOT assign enp3s0 or wlp2s0 "-" inside yast, ip ro will show no routing at all. if insert one of them, it will partly work as long as this connection is ok.
i tried to add a second routing with:
ip route delete default ip route add default via 192.168.0.99 metric 101 dev wlp2s0 ip route add default via 192.168.0.99 metric 102 dev enp3s0
but still the same problem.
then i was thinking try to bond both networkadapters together: in yast i made a bond0
Nononono. It can not be that complicated. :-) NM is easier for laptops. I have it working with Network Manager and it is trivial. I did not need to configure routing at all. Everything on DHCP - if you want fixed IPs, just take a note of gateway and routing, and use the same on your manual config: only the IP changes. I have eth0 where I am now, but my routing this instant is:
Legolas:~ # route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface default 192.168.1.1 0.0.0.0 UG 600 0 0 wlan1 192.168.1.0 0.0.0.0 255.255.255.0 U 600 0 0 wlan1 Legolas:~ #
At least in my case the gateway is the same in both connections. When both are up, the metric is different. Things get complicated if you want both interfaces to have the same IP. -- Cheers / Saludos, Carlos E. R. (from openSUSE 15.0 (Legolas))
Hi carlos, Am 30.09.18 um 21:43 schrieb Carlos E. R.:
Nononono. It can not be that complicated. :-) NM is easier for laptops.
did you have a idea how to go back to network-manager? i switched in yast to nm rebooted, but network was not present at all, and both networkadapters where inside yast grey, not editable. :-((((((((( simoN -- www.becherer.de/AGB -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On 01/10/2018 06.00, Simon Becherer wrote:
Hi carlos,
Am 30.09.18 um 21:43 schrieb Carlos E. R.:
Nononono. It can not be that complicated. :-) NM is easier for laptops.
did you have a idea how to go back to network-manager? i switched in yast to nm rebooted, but network was not present at all, and both networkadapters where inside yast grey, not editable. :-((((((((( Yes, of course, YaST understands that they are handled by NM now, not YaST. YOu have to see NetworkManager now.
Procedure is normally to switch to NM in YaST, and without rebooting try the NM applet in your desktop of choice, and configure network there as needed. If NM does not start, try "rcnetwork restart", try nm again, if not then log out of desktop session, and log back in. Or try another desktop session. As last resort reboot. -- Cheers / Saludos, Carlos E. R. (from openSUSE 15.0 (Legolas))
Hi, carlos, i managed finally to get it with wicked running. the problem was when bonding it did not use the hardwareaddress from the wifi adapter any more, it will use the hardwareaddress from the first bond adapter (lan adapter) and this hw address was not allowed to connect to my wifi network :-(((((((( is now working fine, could unplug lan cable, then (even during data transfer) it switched automatically to wifi, and if cable is back, it switched back. only one question is open: would it be possible to configure more than one wifi network with wicked, (only one adapter inside the computer) to switch automatically to the next one if one of this wifi-network will switched off?? lets say one is on 5ghz other on 2.4 ? simoN -- www.becherer.de -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On 08/10/2018 09.52, Simon Becherer wrote:
Hi,
carlos, i managed finally to get it with wicked running. the problem was when bonding it did not use the hardwareaddress from the wifi adapter any more, it will use the hardwareaddress from the first bond adapter (lan adapter) and this hw address was not allowed to connect to my wifi network :-((((((((
is now working fine, could unplug lan cable, then (even during data transfer) it switched automatically to wifi, and if cable is back, it switched back.
only one question is open: would it be possible to configure more than one wifi network with wicked, (only one adapter inside the computer) to switch automatically to the next one if one of this wifi-network will switched off?? lets say one is on 5ghz other on 2.4 ?
I have no idea, this road you have taken is unknown to me. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
participants (3)
-
Carlos E. R. -
Carlos E. R. -
Simon Becherer