The configuring Ethernet ports in openSUSE, it is possible to say when the port should be configured. This is the STARTMODE= value in the port configuration file. Has there been a deliberate change in the 'onboot' mode? In previous openSUSE releases, this would cause the port to be configured when the system is booted, independent of whether there is a cable attached. If one want to require that there be a cable, STARTMODE can bet set to 'oncable'. In Leap 42,3, it seems that when one selects On Boot in YAST, STARTMODE is set to 'auto'. If there is no cable attached, the port does not get an address. It acts like 'on cable connect'. I am not running Network Manager. The ports are managed in the traditional way (or whatever fills that role these days). The network and related services are all running before anyone logs in. This is a problem in systems that boot along with other hardware. If, say, the Leap machine starts it's network before some other system, the port on Leap will not get an address. This is bad. While plugging in cable (or the remote system turning on) will cause the port to get an address, services that use that port are not restarted. For example, dhcpd will ignore ports without an address - and it will never try again until you actively restart it. Is there any way to get the previous on boot functionality so that ports with fixed address are assigned them on boot, no matter what may or may not be connected to them? -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org