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

TProxy nftables rule clarification #35

Closed
unidcml opened this issue Sep 18, 2024 · 2 comments · Fixed by #37
Closed

TProxy nftables rule clarification #35

unidcml opened this issue Sep 18, 2024 · 2 comments · Fixed by #37
Assignees

Comments

@unidcml
Copy link
Contributor

unidcml commented Sep 18, 2024

The documentation suggests using the nftables rule

socket transparent 0 counter return

It looks like this rule is preventing new connections from being established to TProxy. I suggest using this rule instead

ct state != new socket transparent 0 counter return
@haruue haruue self-assigned this Sep 19, 2024
@haruue
Copy link
Collaborator

haruue commented Sep 19, 2024

Thank you for the suggestion!

Would you please create a Pull Request for it?

You can find the source of the TPROXY docs here.

@unidcml
Copy link
Contributor Author

unidcml commented Sep 20, 2024

According to iptables-extensions man page the rule

iptables -t mangle -A HYSTERIA -m socket -j RETURN

ignores wildcard-bound sockets.

So the correct alternative for nftables is

socket transparent 0 socket wildcard 0 counter return

In my case this solved all connection problems.

This was referenced Sep 20, 2024
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 a pull request may close this issue.

2 participants