mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #327] Network namespace slows Firefox to a crawl #230
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#230
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 @chiraag-nataraj on GitHub (Feb 27, 2016).
Original GitHub issue: https://github.com/netblue30/firejail/issues/327
I'm not entirely sure what's going on - maybe I just don't understand the way network namespaces work. When I try to run Firefox with the
--net=wlan0option, it slows to a crawl. Thinking that it might be thenetfilterin the default profile, I added--ignore=netfilter, but Firefox was still just as slow. I then used--join-network=<pidof iceweasel>and attempted to ping google.com, which failed. Frustrated, I did a simplefirejail --net=wlan0 --noprofile bashand again triedping4 google.comwhich again didn't work. I thought--net=wlan0(or an equivalent command) was not supposed to deny internet access? What's going on? I testedping4 google.comon the regular system and it works fine.[Note]: I'm using firejail 0.9.38.
@netblue30 commented on GitHub (Feb 27, 2016):
--net and --interface are not supported on wlan interfaces. The kernel cannot attach a macvlan driver to them, I'll have to add a note in the man page, thanks for pointing it out.
@chiraag-nataraj commented on GitHub (Feb 27, 2016):
Ah okay thanks!