mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #2232] Support iptables with nf_tables backend #1503
Labels
No labels
LTS merge
LTS merge
bug
bug
converted-to-discussion
doc-todo
documentation
duplicate
enhancement
file-transfer
firecfg
firejail-in-firejail
firetools
graphics
help wanted
information_old
installation
invalid
modif
moved
needinfo
networking
notabug
notourbug
old-version
overlayfs
packaging
profile-request
pull-request
question
question_old
removal
runtime-permissions
sandbox-ipc
security
stale
wiki
wiki
wontfix
wordpress
workaround
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/firejail#1503
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @deb75 on GitHub (Nov 2, 2018).
Original GitHub issue: https://github.com/netblue30/firejail/issues/2232
Hello,
I run
firejailondebian buster. After an upgrate I suddenly got this error :with the command
firejail --private --net=wlp1s0 firefox-esr,wlp1s0being my wifi card.I do not have any error with just :
firejail --private firefox-esr.It seems to be an issue with
iptablesrules, but I am unable to understand, wouldyou have nay hints ?
Best regards
@deb75 commented on GitHub (Nov 5, 2018):
Hi,
I am getting stuck with this issue, googling part of the error message does not lead to any hints.
It seems that there had been some changes in
iptablespackages which are not yet reflected infirejail, but it is little out of scope for me for now.I am happy with any help, I am pretty sure other people face this issue
@netblue30 commented on GitHub (Nov 5, 2018):
Probably the new version of iptables is creating the problem.
@deb75 commented on GitHub (Nov 5, 2018):
Hi,
Thanks for coping with this issue, if you need me to test anything, please ask.
Regards
@reinerh commented on GitHub (Nov 6, 2018):
Are you by chance using Debian?
Since 1.8.1 by default the nf_tables backend is used instead of the xtables backend.
See NEWS.Debian: https://sources.debian.org/src/iptables/1.8.1-2/debian/NEWS/
You can try switching to the legacy mode with the following command (assuming Debian):
update-alternatives --set iptables /usr/sbin/iptables-legacy@deb75 commented on GitHub (Nov 7, 2018):
Hi
You guessed right and your hack makes
firejailwork again.Thanks 👍
@reinerh commented on GitHub (Nov 7, 2018):
Thanks for confirmation. I'll keep it open and change to an "enchancement" bug for nf_tables support.
@ErenjeSimon commented on GitHub (Feb 4, 2022):
Thank you @reinerh update-alternatives --set iptables /usr/sbin/iptables-legacy worked for running nipe and anonsurf on WSL2 debian (kali linux)