mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #1236] cannot use a bridge that has no IP address #842
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#842
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 @voidzero on GitHub (Apr 20, 2017).
Original GitHub issue: https://github.com/netblue30/firejail/issues/1236
When I try to bind a veth to a bridge that has no IP address, I currently get:
This is defined here: https://github.com/netblue30/firejail/blob/master/src/firejail/profile.c#L349 and it also happens for a bridge without IP addresses.
The reason I want to do this is that the bridge has an lxc container configured to it, and the host doesn't need an IP address so I'd rather not give it one. The idea is that the firejailed instance uses the lxc container as a gateway.
@netblue30 commented on GitHub (Apr 20, 2017):
What command do you use to start the sandbox?
@voidzero commented on GitHub (Apr 20, 2017):
Something like this:
192.168.1.1 exists on the bridge, just not on the host.. it is owned by the lxc container. The bridge doesn't have an IPv6 address either - I run
echo 1 > /proc/sys/net/ipv6/conf/br1/disable_ipv6after the bridge is created. So from the host's vantage point it's kind of like a networking switch.As a workaround, I add 192.168.1.254 to the bridge before starting firejail, and remove it once it's running. No issues, tcpdump shows me that everything works exactly how I hoped.
If you do want an extra check, maybe something like
--bridge-no-ipwould work so that the user can indicate being aware of the bridge not having an IP address.@voidzero commented on GitHub (Aug 14, 2017):
@netblue30 hope it's ok for me to ping you on this 😉
@netblue30 commented on GitHub (Aug 18, 2017):
Sure, no problem. I'll change it to an enhancement, and implement --bridge-no-ip as you suggested.
@rusty-snake commented on GitHub (Jul 10, 2019):
Any progress here?
@pallaswept commented on GitHub (Dec 9, 2025):
Bump ;)