It sounds a little like it might be that Network-Manager is configuring things in “User” mode (rather than “System”). https://doc.opensuse.org/documentation/leap/reference/html/book-opensuse-ref... (SECTION 28.4.1) This forum has the same question as you, but no satisfactory answers that I found: https://forums.opensuse.org/showthread.php/513386-Wireless-network-specific-... YaST, to my knowledge, does not have an way to manage per-SSID profiles. But: you can use NM to set various SSIDs into different profiles (i.e. “Cafe”). My thinking runs like this: 1) Use YaST to set up 2 profiles: “Home” and “Cafe” (for example) with permissions set as you want 2) Using NM (as “system”) assign the Wifi@Home to “Home” and other SSIDs/networks to “Cafe” I had to do very nearly the same thing to get SSH working on ethernet for a machine but NOT on Wifi (albeit on the same network). Cameron
On Mar 18, 2021, at 16:17, James Knott <james.knott@jknott.net> wrote:
On 2021-03-18 4:11 p.m., Cameron Cumberland wrote:
If you set the zone via YaST, do changes persist across reboots? I am aware there are some difficulties between Network-Manager and YaST system (and a host of/different/ issues with Wicked), but am not incredibly well versed on the internal functions of either.
I tend to shy away from the Network-Manager GUI for configuring anything deeper than “Wifi On/Off", as it feels buggy in my experience and is prone to interesting visual quirks.
At the moment, I'm focused on why the firewall isn't running.
Here's what the details show:
firewalld.service - firewalld - dynamic firewall daemon
Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled; vendor preset: disabled)
Active: inactive (dead)
Docs: man:firewalld(1)
Is it possible to assign a zone to SSID in Yast?
As I said. at the moment, the firewall isn't even running. Until I get that resolved, there's no point in worrying about zones and SSIDs. On 2021-03-18 4:30 p.m., Cameron Cumberland wrote:
It sounds a little like it might be that Network-Manager is configuring things in “User” mode (rather than “System”).
https://doc.opensuse.org/documentation/leap/reference/html/book-opensuse-ref... (SECTION 28.4.1)
This forum has the same question as you, but no satisfactory answers that I found: https://forums.opensuse.org/showthread.php/513386-Wireless-network-specific-...
YaST, to my knowledge, does not have an way to manage per-SSID profiles. But: you can use NM to set various SSIDs into different profiles (i.e. “Cafe”).
My thinking runs like this:
1) Use YaST to set up 2 profiles: “Home” and “Cafe” (for example) with permissions set as you want 2) Using NM (as “system”) assign the Wifi@Home to “Home” and other SSIDs/networks to “Cafe”
I had to do very nearly the same thing to get SSH working on ethernet for a machine but NOT on Wifi (albeit on the same network).
Cameron
On Mar 18, 2021, at 16:17, James Knott <james.knott@jknott.net> wrote:
On 2021-03-18 4:11 p.m., Cameron Cumberland wrote:
If you set the zone via YaST, do changes persist across reboots? I am aware there are some difficulties between Network-Manager and YaST system (and a host of/different/ issues with Wicked), but am not incredibly well versed on the internal functions of either.
I tend to shy away from the Network-Manager GUI for configuring anything deeper than “Wifi On/Off", as it feels buggy in my experience and is prone to interesting visual quirks. At the moment, I'm focused on why the firewall isn't running.
Here's what the details show:
firewalld.service - firewalld - dynamic firewall daemon
Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled; vendor preset: disabled)
Active: inactive (dead)
Docs: man:firewalld(1)
Is it possible to assign a zone to SSID in Yast?
On March 18, 2021 8:30:14 PM UTC, Cameron Cumberland <cameron.cn@yagowap.com> wrote: ...
1) Use YaST to set up 2 profiles: “Home” and “Cafe” (for example) with permissions set as you want 2) Using NM (as “system”) assign the Wifi@Home to “Home” and other SSIDs/networks to “Cafe”
Yes. Good. I like. I would add: 0) No internet... for those situations where there is no internet connection, or for when you don't want to connect to the internet.
participants (3)
-
Cameron Cumberland -
James Knott -
ken