Thanks, I had a look and I wanted to ask even though it is kinda obvious but I want to confirm about the “community packages”. Who is building them? The word community implies that it may be a community behind them but the naming system suggests that they are personal repos (and most probably not checked). What is the case?
They’re repos maintained by a single person, and official documentation tells you to avoid them, cause their purpose is to be a place where maintainers can break unimportant stuff.
If something is only available through community repos, the official way forward would be to submit a bug report to OpenSUSE, asking to include the package in the official repo, or to contact the maintainer and ask them to do it.
I’d keep use of community repos to a minimum and prefer first flatpak, then the experimental repo over them. No one but the maintainer themselves checks or tests the community repos for stability and compatibility.
But I’ve activated one community repo for a package that wasn’t available anywhere else (sane-airscan).
I see. Yes, it is as I had suspected and yes, as there is not any guarantee that the package is legit unless you know the maintainer, then I also think it is better to avoid. Thanks for explaining
I haven’t used openSUSE in a year or two, but I did really like it. You can easily adjust the Grub timeout with YaST. It was under System > Bootloader.
I ultimately stopped using openSUSE because I kept getting conflicts with zypper and Packman, but that was probably my fault. If you’re on Discord, the openSUSE server is one of the more friendly ones I’ve seen and very helpful.
I think the problem is that you're adding a subnet mask (/24) to your IPs. They should either be bare or have a /32 mask. The /24 mask is allowing the whole 192.168.0.1-254 address range.
Thank you so much, removing the subnet part actually fixed it!! I thought I’d have to be more specific than just the IP, but listing them bare is apparently how you do it.
openSUSE
Active