On Thu, 6 Apr 2017 18:01:07 -0400 Brian K. White wrote:
2) crap: Edit /etc/sysconfig/network/ifcfg-eth0 (or whatever the equivalent is these days, this is from 11.4 using ifcfg, not leap and not using networkmanager. But there IS some equivalent file you can edit.) Then issue a "reboot -r now" and cross your fingers Notwithstanding all of your valid points, which I generally concur with, the last situation like this that I was forced to contend with, I wrote a 'scriptlet' that would restore the original, known working network configuration and reboot five minutes after booting if I'd botched things up. Just a thought ... ;-) This looks like a very good idea. One practical problem can be, that you had to find all relevant configuration files for the backup/restory
Carl Hartung wrote: script. Sometimes network related settings can be found in unusual paths like /usr/lib/udev/rules.d/80-net-setup-link.rules. Today I resolved the problem on the server console. Probably I ran into a Yast problem in network settings module. I only changed the bridge device br0, which was connected to the real network device eth0, from a static IP to DHCP. But after that, I had a lot of configuration errors, probably caused by YaST errors, but maybe caused by a wrong usage or by failures before: - the bridge has forgotten the member eth0 - the routes file became empty - the default gateway was unset and not taken from the DHCP settings Greetings, Björn -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org