mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #4687] Error ioctl: interface.c:302 net_if_mac: Operation not supported when using wifi interface with Unicast MAC #2749
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#2749
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 @svc88 on GitHub (Nov 14, 2021).
Original GitHub issue: https://github.com/netblue30/firejail/issues/4687
Description
This issue only occurs when using a Unicast MAC address on wireless interface.
If you remove the
--maccompletely, it will execute the xterm just fine.Steps to Reproduce
firejail --net="wlp3s0" --dns="1.1.1.1" --mac="EA:29:F8:92:B6:7C" xtermExpected behavior
I expect to be able to use wireless interface wlp3s0 with a random MAC address just as im able to do it on a normal eth0 interface.
Actual behavior
Behavior without a profile
nothing changed.
Environment
Checklist
/usr/bin/vlc) "fixes" it).https://github.com/netblue30/firejail/issues/1139)browser-allow-drm yes/browser-disable-u2f noinfirejail.configto allow DRM/U2F in browsers.--profile=PROFILENAMEto set the right profile. (Only relevant for AppImages)@svc88 commented on GitHub (Nov 14, 2021):
https://github.com/netblue30/firejail/issues/3000 could possibly be a duplicate, as the OP did not mention if he was using --mac, so not sure as he also didnt post a log of the output. Either way, the issue persists with --mac option