From: robin_listas@es.invalid   
      
   On 10/10/2021 23.34, Sidney_Kotic wrote:   
   > So I rebuilt one of my computers, brought it up to Leap 15.3 and that   
   > necessitated a repartition of the drive.  Afterwards I discovered it   
   > couldn't rsync or ssh to any of the others.  So I fired off yast and   
   > looked at the Network Settings, nothing strange there.  I decided to   
   > look at one of the other computers, the other 3 are already running   
   > 15.3, fired off yast and changed it from NetworkManager to Wicked so I   
   > could actually see things about the interfaces.  It couldn't rsync or   
   > ssh either!  Went over to a third computer, did the   
   > yast/NetworkManager/Wicked routine and it failed also.  Scratched my   
   > head...seriously considered having a beer...decided to let things go   
   > until the next day.  Went back and reset the 2 computers to   
   > NetworkManager from Wicked, and set the newly rebuilt machine to   
   > NetworkManager instead of Wicked.  Now all are working correctly.  So,   
   > what's the deal with Wicked?   
      
   You did no diagnosis, nothing to see.   
      
      
   >   
   > For the fun of it I took one machine and set it for Wicked, rebooted:   
   > ip a   
   > 1: lo:  mtu 65536 qdisc noqueue state UNKNOWN   
   > group default qlen 1000   
   >     link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00   
   >     inet 127.0.0.1/8 scope host lo   
   >        valid_lft forever preferred_lft forever   
   >     inet6 ::1/128 scope host   
   >        valid_lft forever preferred_lft forever   
   > 2: eth0:  mtu 1500 qdisc mq state UP   
   > group default qlen 1000   
   >     link/ether 30:9c:23:60:da:33 brd ff:ff:ff:ff:ff:ff   
   >     altname enp8s0   
   >     inet 10.10.13.2/32 scope global eth0   
   >        valid_lft forever preferred_lft forever   
   >     inet6 fe80::329c:23ff:fe60:da33/64 scope link   
   >        valid_lft forever preferred_lft forever   
   > 3: wlan0:  mtu 1500 qdisc mq state UP   
   > group default qlen 1000   
   >     link/ether f4:28:53:18:42:7e brd ff:ff:ff:ff:ff:ff   
   >     altname wlp5s0   
   >     inet 192.168.1.3/24 brd 192.168.1.255 scope global wlan0   
   >        valid_lft forever preferred_lft forever   
   >     inet6 fe80::f628:53ff:fe18:427e/64 scope link   
   >        valid_lft forever preferred_lft forever   
   >   
   > ip route   
   > default via 192.168.1.1 dev wlan0 proto dhcp   
   > 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.3   
   >   
   > Switch to NetworkManager, no other change and no reboot, and...   
   > ip route   
   > default via 192.168.1.1 dev wlan0 proto dhcp metric 600   
   > 10.10.13.0/24 dev eth0 proto kernel scope link src 10.10.13.2 metric 100   
   > 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.3 metric 600   
      
   So?   
      
   --   
   Cheers,   
          Carlos E.R.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)