mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #7054] Add link-local addresses to 'nolocal' firewall configs #3467
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#3467
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 @cobratbq on GitHub (Feb 6, 2026).
Original GitHub issue: https://github.com/netblue30/firejail/issues/7054
Description
I've noticed that
nolocal.net/nolocal6.netdo not have rules for link-local network address ranges. Even though these are not routed, they can still be used to set up local network communication, including services.https://en.wikipedia.org/wiki/Link-local_address
Am I missing something, or should these be included?
169.254/16fe80::...Steps to Reproduce
N/A. Observation based on scripts
nolocal.netandnolocal6.net.Expected behavior
Have link-local address ranges also explicitly blocked?
Actual behavior
Link-local address ranges are not mentioned at all.
Behavior without a profile
N/A.
Additional context
Environment
N/A.
Checklist
firejail version 0.9.74
@netblue30 commented on GitHub (Feb 7, 2026):
All set, thanks for the info!
@kmk3 commented on GitHub (Feb 23, 2026):
Closing as fixed by
46134f6972.