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.
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.
Yes, Printer setup on openSUSE is still a clusterfuck, for reasons. You're best off in openSUSE KDE to just point your webbrowser at http://localhost:631 and log directly into CUPS and setup your printers that way.
If you want all your web video and whatnot to work, you need to install the codecs from Packman, in their entirety, or use a flatpak'd web browser. openSUSE won't ship patent encumbered codecs from the official repositories.
Unless you really know what you're doing, with Leap, or Tumbleweed, stick with the OSS and non-OSS repos provided. They are the ones that have been through the openQA process, and are officially "supported". If you enable a bunch of home:devel: or other repositories, just assume that they're unstable, and use at your own risk. If you're looking at a repository on OBS, and don't see openSUSE_Tumbleweed as one of the build targets, then forcing the install with a Leap or SLE package, may, or may not break things.
Regarding zypper ref and autorefresh, I can't recall exactly, but there is the chance that just running zypper dup and hoping that it refreshes everything on it's own, with non-standard repositories may fail, which can lead to some weird edgecases.
Just in general, you're going to want to run zypper ref && zypper dup (not the other way round) As far as YaST being targetted more at Leap than Tumbleweed, you're exactly right. And there's a reason that we don't ship it with newer flavours of the distribution.
And without YaST, you can set GRUB_TIMEOUT=0 in /etc/default/grub, then run update-bootloader or grub2-mkconfig -o /boot/grub2/grub.cfg as root.
It’s just one of the things I noticed.
Interesting, I can’t post here if I select “English” as the post language.
I get an error 400 HTTP status with a JSON error: “language_not_allowed”.
It works fine if I leave the language as “Undetermined”. Are these just the OpenSuse community settings?
openSUSE
Oldest