Upgrade from 13.1 -> 13.2 removed support for traditional/stable if-up/if-down network control, replacing it with wicked. In 13.2, wicked's currently badly broken; there are existing/critical issues, that prevent production use; those issues include, among mounting others, e.g., (1) tun https://bugzilla.suse.com/show_bug.cgi?id=904903 (2) up/down script usage https://bugzilla.suse.com/show_bug.cgi?id=907215 (3) ipv6 https://bugzilla.suse.com/show_bug.cgi?id=907694 Those issues need fixing, and are getting some attention already. In current state, these network problems leave 13.2 unstable at best, unusable at worst. In 13.1 all the aforementioned issues are not a problem -- everything was working. IMO, disabling working if up/down prior to full-release-vetting of wicked et al is an operational mistake. We'd prefer to stay with 13.2 .... but our available production solutions atm are (1) downgrade 13.2 -> 13.1 (2) switch to a known/working other distribution (Redhat/Centos 7, e.g.) (1) is messy and painful, and functionally regresses many of the OTHER solutions that modern/current 13.2 brings. (2) is what we've done -- currently at all our production/edge boxes. In lieu of immeidate fixes to 13.2, is it possible to reenable 'old' ifup/ifdown networking, disabling wicked, so we can get the distro back to working/production state? Or is wicked simply too wired-into 13.2? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org