Yast had the search and nameservers information in, and it even loaded them back when reopening yast (which surprised me, I expected it to read/store from resolv.conf itself). I work with SAP HANA, SUSE is also the supported OS for it (I've a SUSE sysadmin certification).
I commented about yast being a gui that failed (silently) doing something simple that shouldn't need a gui; I didn't say SUSE isn't reliable.
It had all networking up and running. It just didn't have resolv.conf entries, so no dns.
No, the SUSE demo license had expired before he configured it for the first time, so there was no repo access.
He did everything right in yast, but according to the yast log, it was trying and failing to get wpa-supplicant, although this is a VM with no wifi whatsoever. Yast "finished" the configuration with no errors, but failed to place the required entries in resolv.conf and hosts.
It's just one example of a useless gui trying to make simple things complicated.
Linux is not a company fighting for profits and market share, with software developers paid to work according to the company's strategy.
You want something in Linux that nobody cares to develop? Decelop it yourself or gtfo.
A few hours ago I was helping a GUI-oriented colleague to get network working in a SUSE test installation. He had configured it in yast (a GUI admin interface), but he couldn't get to the internets.
I logged in, got me a command line:
ip a s (it had an inteface with an IP, and it was up).
ip r s (it had a default route to the world)
ping 8.8.8.8 (it worked)
host google.com (didn't work, it's always dns)
vi /etc/resolv.conf (added search and nameservers, there were none).
problem fixed (also suggested him to check his /etc/host, as domainame wasn't set either).
Why on earth do I want a gui to make simple things complicated - and silently fail while trying to do it? (yast couldn't find wpa-supplicant, although this is a VM with no wifi).
IMO, administering Linux through GUI tools is dangerous, because you probably don't know, or don't want to know, exactly what the tool is doing. It makes Linux as "inexplicable" as Windows.
For now. 40 years ago, what it does now was impossible science fiction.
Well, the opressed and enslaved usually has no say about changing the law.
On one hand, great; will that extent to software development, architecture and other fields?
On the other hand, sounds like the first step to, when AI and androids reach self awareness and conscience, legally keep them enslaved.
Linux has a graphical file manager? How bizarre.
When you can pay to win, to always have the last word... He'll let them know.
He's going to be able to harass everyone that had blocked him.
Why do you have two default routes?
The last line in your table also doesn't look right.
I have used yast to configure the network before (not on this host), and it works.
I quickly looked at the yast log, and there were errors looking for wpa-supplicant. I -think- it's because my colleague installed this VM months ago, did not configure it, then went on vacation. Now the SUSE "no license" grace period expired, and the host has no access to the repositories.
If that's the cause, there are two issues: 1. why does it want to install wpa-supplicant if there's no wifi (maybe it's a wicked dependency), and 2. why does it fail silently, concluding the config operation as if it ran ok