mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #1844] Support wireguard interfaces on firejail's --net option #1251
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#1251
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 @Piraty on GitHub (Mar 28, 2018).
Original GitHub issue: https://github.com/netblue30/firejail/issues/1844
Using the
--net=<interface>option does currently not work for wireguard interfaces.I encountered this on a Void Linux System, x86_64 glibc.
linux 4.14.29and lowerwireguard 0.0.20180304firejail 0.9.52Here is an strace of the process:
<removed>@atlaua commented on GitHub (Mar 28, 2018):
Firejail's --net option uses macvlan under the hood and hence only works with L2 ethernet devices (as documented in the man page). Therefore, it can obviously not be used directly with a wireguard tunnel which operates at L3.
@Vincent43 commented on GitHub (Mar 29, 2018):
You can try
firejail --netnswith https://www.wireguard.com/netns/@Piraty commented on GitHub (Mar 29, 2018):
Thanks, i will look into it.
Definetely missed the
L2part in the manpage...