[GH-ISSUE #919] Disable warning for disabled networking #623

Closed
opened 2026-05-05 06:17:55 -06:00 by gitea-mirror · 10 comments
Owner

Originally created by @peterzhu2118 on GitHub (Nov 18, 2016).
Original GitHub issue: https://github.com/netblue30/firejail/issues/919

I have set Firejail to be quiet. If I set networking to be off in firejail.config I get the output Warning: networking features are disabled in Firejail configuration file every time I run something. How can I disable this?

Originally created by @peterzhu2118 on GitHub (Nov 18, 2016). Original GitHub issue: https://github.com/netblue30/firejail/issues/919 I have set Firejail to be quiet. If I set networking to be off in `firejail.config` I get the output `Warning: networking features are disabled in Firejail configuration file` every time I run something. How can I disable this?
gitea-mirror 2026-05-05 06:17:55 -06:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@vn971 commented on GitHub (Nov 18, 2016):

Firejail does have a quiet mode firejail --quiet --noprofile echo 123, would that work for you? It won't print any firejail-specific warnings that way AFAIUnderstand.

In normal mode, firejail does consider the "networking features" thing to be serious enough for a warning.

<!-- gh-comment-id:261672694 --> @vn971 commented on GitHub (Nov 18, 2016): Firejail does have a quiet mode `firejail --quiet --noprofile echo 123`, would that work for you? It won't print any firejail-specific warnings that way AFAIUnderstand. In normal mode, firejail does consider the "networking features" thing to be serious enough for a warning.
Author
Owner

@peterzhu2118 commented on GitHub (Nov 19, 2016):

Even when using the --noprofile flag the firejail.config file is still loaded right? Is there some way of not disabling the profile while not printing the warning?

<!-- gh-comment-id:261680232 --> @peterzhu2118 commented on GitHub (Nov 19, 2016): Even when using the `--noprofile` flag the `firejail.config` file is still loaded right? Is there some way of not disabling the profile while not printing the warning?
Author
Owner

@vn971 commented on GitHub (Nov 19, 2016):

@peterzhu2118 the profile /etc/firejail/default.profile is NOT loaded when you use --noprofile. firejail.config is loaded in all cases.
Not that, if I understand it correctly, firejail prints a warning only when you try to use an unsopported feature. Just disabling "networking" and launching firejail --noprofile does not result in a warning on my system.

<!-- gh-comment-id:261687631 --> @vn971 commented on GitHub (Nov 19, 2016): @peterzhu2118 the profile `/etc/firejail/default.profile` is NOT loaded when you use --noprofile. `firejail.config` is loaded in all cases. Not that, if I understand it correctly, firejail prints a warning only when you try to use an unsopported feature. Just disabling "networking" and launching `firejail --noprofile` does not result in a warning on my system.
Author
Owner

@peterzhu2118 commented on GitHub (Nov 19, 2016):

@vn971 So would it be possible to load that profile without outputting the warning? What do you mean by an "unsupported feature"? Does that mean disabling networking is an unsupported feature?

<!-- gh-comment-id:261688740 --> @peterzhu2118 commented on GitHub (Nov 19, 2016): @vn971 So would it be possible to load that profile without outputting the warning? What do you mean by an "unsupported feature"? Does that mean disabling networking is an unsupported feature?
Author
Owner

@netblue30 commented on GitHub (Nov 19, 2016):

It is a bug, --quiet should have disabled the message. I'll make sure it gets fixed in the next release.

<!-- gh-comment-id:261723245 --> @netblue30 commented on GitHub (Nov 19, 2016): It is a bug, --quiet should have disabled the message. I'll make sure it gets fixed in the next release.
Author
Owner

@peterzhu2118 commented on GitHub (Nov 19, 2016):

@netblue30 When can I expect the next release? I wish I could fix this but unfortunately I don't know C.

<!-- gh-comment-id:261724382 --> @peterzhu2118 commented on GitHub (Nov 19, 2016): @netblue30 When can I expect the next release? I wish I could fix this but unfortunately I don't know C.
Author
Owner

@netblue30 commented on GitHub (Nov 19, 2016):

My plan is to have it out by the end of next week.

<!-- gh-comment-id:261727641 --> @netblue30 commented on GitHub (Nov 19, 2016): My plan is to have it out by the end of next week.
Author
Owner

@peterzhu2118 commented on GitHub (Nov 19, 2016):

@netblue30 Thats great. Thank you so much!

<!-- gh-comment-id:261728162 --> @peterzhu2118 commented on GitHub (Nov 19, 2016): @netblue30 Thats great. Thank you so much!
Author
Owner

@netblue30 commented on GitHub (Nov 20, 2016):

No problem. I'll let you know when is done.

<!-- gh-comment-id:261786472 --> @netblue30 commented on GitHub (Nov 20, 2016): No problem. I'll let you know when is done.
Author
Owner

@netblue30 commented on GitHub (Nov 21, 2016):

All fixed. I would suggest you move on the bugfix branch here: https://github.com/netblue30/firejail/tree/0.9.44-bugfixes - it is more stable, almost ready for a new release.

<!-- gh-comment-id:261957242 --> @netblue30 commented on GitHub (Nov 21, 2016): All fixed. I would suggest you move on the bugfix branch here: https://github.com/netblue30/firejail/tree/0.9.44-bugfixes - it is more stable, almost ready for a new release.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/firejail#623
No description provided.