mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #1721] Firejail does not work with an ipv6-only interface #1162
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#1162
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 @ghost on GitHub (Jan 9, 2018).
Original GitHub issue: https://github.com/netblue30/firejail/issues/1721
This might be somehow related to #1236
Step to reproduce, assuming Ubuntu 16.04 (or kind of Debian derivative)
Now you see you have a working bridged interface with ipv6 only addresses.
Not configured... come on! ifconfig says otherwise...
For the record, other software like VirtualBox are quite happy with that kind of bridged interface. You get an ipv6-only virtual machine. This could be used for example to simulate situations like your mobile provider offering ipv6-only since there is a shortage of ipv4.
@netblue30 commented on GitHub (Jan 17, 2018):
I run into a bug with setting up --ip6=address. It works fine on mainline now:
In this moment I have a bridge device up, without IP configured. I start the sandbox:
I'll bring in a fix for #1236.
@ghost commented on GitHub (Jan 17, 2018):
This is anyway less urgent that #1722 (fixed - to be tested) since running a sandbox with ipv6 only is mainly for test purpose. Unless you are in China where it could make sense, in Europe you will get only 20% of the internet that way... so sure: testing and being sure you have less internet sites possibly bothering you are great with ipv6-only!
@netblue30 commented on GitHub (Jan 18, 2018):
I'll drop the fix for #1236 for now, too much involved. Closing the issue for now. If you run into problems in you testing, open a new issue and reference the old one - it is easier for me to track them this way.
@ghost commented on GitHub (Jan 18, 2018):
Ok, it works for me, thanks! The workaround being to have also an ipv4 stack alongside ipv6, since #1722 is supposed to be solved, there is no issue anymore.
If someone asks for an ipv6-only stack on project (https://github.com/Bylon/TOR_Middlebox) I'll reopen here.