-
Notifications
You must be signed in to change notification settings - Fork 95
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
Protocol decode mismatch and severe packet loss #5
Comments
After some debugging, i think i found what is the problem:
|
Hello, |
This problems seem due to the pppd fail to parsing the frames which sstpd sent. By adding
This one cause by sstpd cannot parsing the frames which pppd sent correctly. I found pppd sent a half frame to sstpd, and follow by a complete one. It is my understanding that the only way to determine the "gap" between each ppp frames |
Ok. Let me know if you found something. |
I found one sstpd implementation written in javascript, but that implementation barely able to survive to open google.com :) anyway there is handling for large ppp frames |
En.. I added the option |
Interesting, with sync i am able to get ip addres 1/10 cases |
Try out the |
It works :)
|
FCS calculation is written in C now. (unsure whether effective) |
thanks i will test all the things |
I have do some profile with vmprofile module for python
|
Hello,
i have just tried your last version there are errors in pppd log about unsupported protocol.
After that errors windows clients expirience severe packet loss that leads to disconnection
logs from pppd
logs from sstpd
The text was updated successfully, but these errors were encountered: