mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #1406] ARP cache pollution when using net namespaces. #958
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#958
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 @caoliver on GitHub (Jul 27, 2017).
Original GitHub issue: https://github.com/netblue30/firejail/issues/1406
On starting a jail with a network namespace, firejail sends an ARP request to determine if the chosen IP address is already in use, but it sends that request with the jail's MAC, but the host's IP. This pollutes the ARP cache on boxes that are listening to that broadcast with a bogus MAC/IP pair resulting in delays when trying to reach the host via the net. The free IP for the jail should be determined on the host and communicated to the jail subsequently upon its creation.
@netblue30 commented on GitHub (Jul 27, 2017):
I put a fix in, you can give it a try. I'm doing the probing with a IP address of 0.
@caoliver commented on GitHub (Jul 28, 2017):
On Thu, 27 Jul 2017 17:20:25 +0000 (UTC)
netblue30 notifications@github.com wrote:
For my initial testing, this seems to work. I'll put this on the rest of my boxes and see how I go.
BTW: RFC 5227 didn't exist when I was last hacking TCP/IP; thanks for the reading material.
Sorry that I whinge so much, but I suppose that you get lots of whinging people when you write a generally useful tool. ;-)
Thanks and Cheers!
--
Christopher Oliver current.input.port@gmail.com
@netblue30 commented on GitHub (Jul 29, 2017):
Actually, I've just found about it now. Searching for the original ARP RFC, the new one came up in Google search. Keep an eye on it, we'll reopen it if necessary. Thanks for the bug.