Only because other Distros are installing it by default?
I think systemd-network is not used by many people, most people are wanting a automatically connection which is done by Networkmanager and dhcp or wicked and dhcp.
I think, people using systemd for setting up their network are knowing what they are doing and also can read manpages.
If you read the package’s change log, you’ll find email address(es) of the maintainer(s). You might inquire of any of them why. A suggestion to file an enhancement request on Bugzilla could result. It wouldn’t surprise me if the reason it’s not a default is that YaST does not (yet) support configuring it. The YaST developers have a mailing list. Asking there could be worth while. Complaining here isn’t often seen by maintainers looking for enhancement requests or things to do.
I find it a simple matter during installation to taboo NetworkMangler and then switch from Wicked to systemdnetwork(d) on the installed system.
If you want it just install it. What is the big deal??? Not at all sure what advantage it offers over the two network clients currently installed by default.
The fact there is no current Yast module is a big deal for most openSUSE users.
Hi
Because, that is the desired application to use on openSUSE as decided by the maintainers, desktop integrator’s, those that do etc.
If persons X,Y and Z want application ABC to be a default, then maintain it integrate it, test it and agree to maintain going forward for all openSUSE users, there is nothing whatsoever in the way of that happening, those that ‘do’ ‘decide’.
sure there is no issues i can install it by default but it was like i know as i was a fedora ask so i know there are lots of user use this to set DnsOverTls and as i have told you most major distros include this package so i request to add this by default
none the less if you want it you will lookinto else we need to find what is missing which is frustrating.
Your request to have that package included by default will not be addressed on these forums, you need to contact the maintainers, as outlined in post #22.
I feel however you will need a far stronger argument for it’s inclusion than “other distributions include it by default”.
This is the address of the author of these changes. This person may or may not be maintainer of the package - it is not uncommon for someone to submit a fix to some package without being maintainer. Mailing random addresses has small chance of being successful. At the very least one should check OBS for users listed as direct maintainers or preferably bug owners of the package.
Besides, this is usual example of substituting the goal with the means to achieve it. The goal is to have DoT. systemd-resolved is just one possible way to do it, but just including the binary by defaults is not going to magically solve it. It needs complex changes, possibly across multiple packages. So, factory mailing list would be a better place to start this discussion.
P.S. quite a lot of users simply use whatever DNS servers their ISP give them, and these servers probably do not support DoT anyway. And if user is capable of configuring systemd-resolved manually, I suspect installing it is the smallest problem.
Here is one of those distributions that installs resolved by default and even uses it by default - Ubuntu 22.04.
bor@bor-Latitude-E5450:~$ resolvectl
Global
Protocols: -LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
resolv.conf mode: foreign
...
Link 3 (wlp2s0)
Current Scopes: DNS
Protocols: +DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Current DNS Server: 192.168.1.1
DNS Servers: 192.168.1.1 fe80::1%21943
So the mere existence of systemd-resolved does not mean DoT is magically used and if user knows that DoT is needed and knows how to set it up user most certainly does not have any issue with installing one extra package.
i think request from your end makes more sense and i will can one of you do it also and definitely a email by you makes stuff easier and more important
Setting up 1.1.1.1 takes two minutes and requires no technical skill or special software. Even if you’re a computer novice, pick your device below for an easy-to-follow setup guide.
While these steps are for Ubuntu, most Linux distributions configure DNS settings through the Network Manager. Alternatively, your DNS settings can be specified in /etc/resolv.conf
Click the Applications icon on the left menu bar.
Click Settings
, then Network. 1. Find your internet connection on the right pane, then click the gear icon.
Click the IPv4
or IPv6 tab to view your DNS settings. 1. Set the “Automatic” toggle on the DNS entry to Off
.Provide the 1.1.1.1 DNS addresses in the DNS entries field:
For IPv4: 1.1.1.1
and 1.0.0.1 - For IPv6: 2606:4700:4700::1111,2606:4700:4700::1001
Click Apply
, then restart your browser. 1. You’re all set! Your device now has faster, more private DNS servers
open suse lacks polish that we get with debian or redhat fedora base distros suse lacks many stuff like systemd-resolved was not included and does not work as it should be i find most of the apps are not using my set dns and connectivity check also does not work in suse it need serious work
Who is forcing you to use openSUSE (please, as long as you still are posting here, try to spell it correct)?
When it frustrates you, please stop using it for your own health.
Use what you like. There is a reason that there are more Linux distributions then only one.