Skip to content
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

ProxyPair structure should save socket inodes #127

Open
dma opened this issue Oct 1, 2017 · 0 comments
Open

ProxyPair structure should save socket inodes #127

dma opened this issue Oct 1, 2017 · 0 comments

Comments

@dma
Copy link
Contributor

dma commented Oct 1, 2017

Current procsnitch lookup works, but subject to losing information about short lived connections.

  • The socket inode #s should be saved when oz TCP port forward clients connect, and removed when disconnect, though there may be reason to keep the information longer than the life of the connection, perhaps a ring buffer
  • This ensures that every connection is recorded by oz-daemon, even if it is lost immediately.
  • The procsnitch lookup should rely on the inode first. Inodes for sockets can be retrieved via INET_DIAG.
  • This will result in a more efficient lookup by fw-daemon, the connection monitor, and elsewhere (see Implement experimental socket monitoring via INET_DIAG netlink interface go-procsnitch#6)
@dma dma changed the title ProxyPeers should save socket inodes ProxyPair structure should save socket inodes Oct 1, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant