Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • P Plasma Firewall
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Bugzilla
    • Bugzilla
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • PlasmaPlasma
  • Plasma Firewall
  • Issues
  • #16
Closed
Open
Issue created Jan 22, 2021 by Kevin Kofler@kkoflerDeveloper

Support firewalld zones

(I am filing this here because there does not seem to be a component at https://bugs.kde.org/ for this project yet.)

Firewalld has a central concept called "zones". Those are the main setting to make in the firewalld. They correspond to a whole profile of rules. All rules are part of one or more zones. Switching the zone switches the entire rule set. (Those zones are implemented deep in the backend, not in the UI, i.e., the UI should use the backend's zones and not attempt to come up with its own.) Think of it as the equivalent of sysv runlevels or systemd targets, but for a firewall.

Unfortunately, this concept does not seem to be implemented in Plasma Firewall yet.

Edited Jan 22, 2021 by Kevin Kofler
Assignee
Assign to
Time tracking