-
Notifications
You must be signed in to change notification settings - Fork 569
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for ipvlan interfaces #1978
Comments
Let me give it a try, thanks for the idea! |
All in mainline, you can try it out, in your case:
|
Hmm, I tried something as simple as |
@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 |
@netblue30 I can't see where |
Something didn't got merged! Let me take a look, thanks! |
Should be all fixed now: b78cc58 |
Firejail adds new macvlan interface when
--net
option 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:
The text was updated successfully, but these errors were encountered: