Skip to content

Conversation

@nickgarlis
Copy link
Contributor

Associate netlink errors with the specific NFT operations that produced them.

  • Add nftMsgType with a String() method to replace sys/unix constants
  • Add handleReceiveError to match errors to their originating messages
  • Add withOpError to assist in handling netlink.OpError values

This updates errors from:

receive: netlink receive: no such file or directory

to:

receive: NFT_MSG_NEWCHAIN: netlink receive: no such file or directory

Associate netlink errors with the specific NFT operations that
produced them.

- Add nftMsgType with a String() method to replace sys/unix
  constants
- Add handleReceiveError to match errors to their originating
  messages
- Add withOpError to assist in handling netlink.OpError values

This updates errors from:

    receive: netlink receive: no such file or directory

to:

    receive: NFT_MSG_NEWCHAIN: netlink receive: no such file or directory
@nickgarlis nickgarlis force-pushed the add-error-message-tracing branch from e1961e6 to b1a046b Compare November 6, 2025 16:25
@stapelberg stapelberg merged commit 3ac3a49 into google:main Nov 10, 2025
2 checks passed
@stapelberg
Copy link
Collaborator

Thanks!

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

Successfully merging this pull request may close these issues.

2 participants