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

lb: backend traffic should not be classified/filtered #74

Closed
vdmit11 opened this issue Mar 11, 2015 · 1 comment
Closed

lb: backend traffic should not be classified/filtered #74

vdmit11 opened this issue Mar 11, 2015 · 1 comment
Assignees

Comments

@vdmit11
Copy link
Contributor

vdmit11 commented Mar 11, 2015

Currently, the classification/filtering functions are called for all sockets owned by the Tempesta FW.

However, they should be called only for client sockets. There is not much sense in filtering the internal backend traffic. Usually we can trust the internal network and would not like to inspect its traffic.

@krizhanovsky
Copy link
Contributor

Actually, we do need to process backend traffic and WAF is one of the cases. Rather classification logic should just skip packets which aren't interesting for its analyzing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants