mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #1978] Add support for ipvlan interfaces #1327
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#1327
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 @ValdikSS on GitHub (Jun 4, 2018).
Original GitHub issue: https://github.com/netblue30/firejail/issues/1978
Firejail adds new macvlan interface when
--netoption is specified. While macvlan is a best choice for Ethernet interfaces, it doesn't work with 802.11 Wi-Fi.Right now there's no easy way to use Wi-Fi with Firejail. Documentation describes routed setup, which @netblue30 recommends to use in #1600.
Linux kernel contains another interface driver which is very similar to macvlan and works with Wi-Fi: ipvlan. Contrary to macvlan, it shares the same MAC address as the master interface, which allows it to be used with 802.11.
@netblue30, is it possible to auto-detect interface type and use either macvlan for Ethernet and ipvlan for 802.11?
Here's how you can create this interface and use it in Firejail:
@netblue30 commented on GitHub (Jun 4, 2018):
Let me give it a try, thanks for the idea!
@netblue30 commented on GitHub (Jun 12, 2018):
All in mainline, you can try it out, in your case:
@chiraag-nataraj commented on GitHub (Jul 9, 2018):
Hmm, I tried something as simple as
firejail --noprofile --net=wlp60s0and wasn't able to connect with the outside world. Trying to ping a host would resolve but time out with destination unreachable. Am I doing something wrong? Is there some extra preparation that needs to happen for this to work properly?@ValdikSS commented on GitHub (Jul 18, 2018):
@netblue30 it indeed doesn't work for some reason. It doesn't add default route, but adding it manually does not fix the issue. Are you sure you set up ipvlan of
type l2?@ValdikSS commented on GitHub (Jul 18, 2018):
@netblue30 I can't see where
IPVLAN_MODE_L2is defined. It looks like there are no changes to automake/autoconf, and nobody defines it.@netblue30 commented on GitHub (Jul 24, 2018):
Something didn't got merged! Let me take a look, thanks!
@netblue30 commented on GitHub (Jul 25, 2018):
Should be all fixed now:
b78cc58693