-
Notifications
You must be signed in to change notification settings - Fork 69
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
Kernel panic on high traffic #43
Comments
Hi, Any update on this? We are going to do the same. Tested successfully locally and going to deploy on a production server (Ubuntu Server 16.04 64) with 2Gbps traffic. Thanks. |
Can anyone confirm anything about the state? |
I can test it in a week or two.
…On Thu, Nov 24, 2016, 12:26 Eliezer Croitoru ***@***.***> wrote:
Can anyone confirm anything about the state?
I can only try to build and run it but if someone is using the current
branch please let me know how it works.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#43 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ARVaENGQ5lC1wUlwhVkmzfsOJSj-CE7dks5rBayUgaJpZM4Koh9x>
.
|
@IvnSoft Good for me. |
@elico Still kernel panic on high traffic, tried latest commit from master on a 1Gbit/s line. Takes a couple of hours before the kernel panic happens. |
Hi guys.
I was using this solution with iptables, to classify traffic and assign it so specific qdiscs (htb or hfsc)
It worked ok for test traffic, but as soon as i tried to apply a single rule to the whole network (about 1gbps traffic, trying to shape quic protocol) the system lasted about 5-10 minutes, and then kernel panic.
This was done in a Fedora 20 64bits server, kernel 3.16.6-200, using everthing cloned from this git.
I wont be able to reproduce it soon as this is a production server (and the crash doesnt appear in other low-traffic servers). But i can test some times in the night.
The text was updated successfully, but these errors were encountered: