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

[Feature Request] "Final" Rule Action #2340

Open
mazzz1y opened this issue Dec 5, 2024 · 2 comments
Open

[Feature Request] "Final" Rule Action #2340

mazzz1y opened this issue Dec 5, 2024 · 2 comments

Comments

@mazzz1y
Copy link
Contributor

mazzz1y commented Dec 5, 2024

The idea of rule actions is awesome.

I suggest implementing a rule action that forwards the connection to the "final" outbound, skipping the processing of the next rules. This would be helpful in complex configurations.

Currently, we need to specify the outbound explicitly for each rule, which isn't convenient when there are too many rules with the same outbound.

{
  "action": "final"
}
@neerro
Copy link

neerro commented Dec 7, 2024

What you suggested is completely unclear in which scenarios this could be useful. Could you elaborate on the essence of the idea in more detail?

@mazzz1y
Copy link
Contributor Author

mazzz1y commented Dec 8, 2024

This action means "stop processing the subsequent rules and set the outbound to default"

For example, for certain specific connections, we don't need sniffing and want to route them out as early as possible.

This allows us to release the connection without explicitly setting the outbound, using default(final) outbound.

But it might be better to use the existing "route" action without setting the outbound. However, this field is currently required

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

2 participants