Bug 12643 - QoS killing IPSec tunnel throughput
Summary: QoS killing IPSec tunnel throughput
Status: CLOSED FIXED
Alias: None
Product: IPFire
Classification: Unclassified
Component: ipfire-release (show other bugs)
Version: 2
Hardware: x86_64 Unspecified
: - Unknown - Major Usability
Assignee: Arne.F
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-06-17 18:31 UTC by Ian -
Modified: 2023-12-07 07:46 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ian - 2021-06-17 18:31:26 UTC
Hello please see thread https://community.ipfire.org/t/ipsec-tunnel-crippled-by-qos/5619

It seems that QoS is halving my throughput using IPSec.

Only turning off QoS seems to fix.

I have correctly classified the VPN traffic, even put the iperf traffic into the VPN category so that all traffic is the one category. I ensure that the maximum bandwidth is at my maximum bandwidth, and yet it absolutely smashes my ipsec tunnel.

I am unsure if it is related to the other bug that has been closed as not a bug, but for me this seems to be a bug, the only work around is to totally turn off QoS.

My fireinfo
https://fireinfo.ipfire.org/profile/2e62a4891269f0e9d5b070ecf08ad99706dd153a
Comment 1 Michael Tremer 2021-06-18 09:10:53 UTC
It looks like we mark the internal IPsec traffic and send it through the subclasses which should not happen. Instead we should skip processing all of the marking rules inbound and outbound for any packet that is received from or being sent to an IPsec network.

Ian, can you confirm that traffic is halved in both inbound and outbound direction or just one?
Comment 2 Ian - 2021-06-18 10:41:34 UTC
(In reply to Michael Tremer from comment #1)
> Ian, can you confirm that traffic is halved in both inbound and outbound
> direction or just one?

My outbound link is only ~12mbits and I am achieving ~11mbits out, so definitely not halved going out, however is it still throttled? I fear my uplink isn't fast enough to know for sure.
Comment 3 Ian - 2021-06-27 05:09:10 UTC
Hi,

Is there a work around for this issue until it is fixed? Some IPTables commands or something?

Thanks
Comment 4 Ian - 2021-06-30 03:07:43 UTC
Hi there,

Just checking if this is being worked on as there hasn't been any further comments or updates since I was last asked to provide information.

Not trying to rush you, just want to know if it is being worked on.
Comment 5 Arne.F 2021-07-21 12:41:43 UTC
Im run into the same problems that is the reason why michael has assignend this to me. 

The problem is the kernel internal handling of IPSec traffic that runs two times through the IPTables stack. In upstream direction there is a rule that prevent from double counting but in downstream there is a bug.

At the moment i have to finish some other things first...