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

CPU usage #70

Open
Shamanky opened this issue Aug 2, 2024 · 1 comment
Open

CPU usage #70

Shamanky opened this issue Aug 2, 2024 · 1 comment

Comments

@Shamanky
Copy link

Shamanky commented Aug 2, 2024

Have you tested this module under high load e.g. 700Mb(megabits)/s , 5000Mb(megabits)/s. I am mainly interested in CPU load.

@Lochnair
Copy link
Owner

Lochnair commented Aug 2, 2024

Can't say I have.
But a more relevant metric here than throughput is how many new TLS connections you have per second. So if you set up your firewall to only run the handshake through xt_tls, then the CPU load should be pretty negligible.

For example if you have this:

# iptables -L -v
Chain INPUT (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination

Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination

Chain OUTPUT (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination
    0     0 DROP       tcp  --  any    any     anywhere             anywhere             tcp dpt:https TLS suffix-match hostset blocklist
    0     0 ACCEPT     tcp  --  any    any     anywhere             anywhere             tcp dpt:https

Then every single packet on port 443 will go through xt_tls, in which case - yes high throughput might cause extra CPU load while using this module.

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