canonical / canonical/multipass

firewalld integration

Open
#1,236 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

connectivity (firewall) good first issue help wanted
Dominant language
C++
Stars
9.2k
Forks
829
Avg merge
3d 2h
Merged PRs (30d)
45

Description

Kind of related to #533. I use firewalld, which configures the traffic filtering rules via nftables, rather than iptables. Not stopping firewalld or forgetting to move the mpqemubr* interface to the right zone results in problems launching the instances. AFAIK libvirt integrates with firewalld by setting up a separate zone for the bridge interface.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing related issue #533 and the instance-launch path described here. Compare the current handling of the mpqemubr* interface with libvirt's firewalld behavior and determine how the bridge should be assigned to its own zone. Done means instances launch without manually stopping firewalld or moving the interface.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp, linux
Domain
networking, operating-systems
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.