On Wed, Aug 5, 2015 at 10:11 AM, yick xie <yick.xie at gmail.com> wrote: > Hi developers > Firstly, let me have a introduction of my case > A TCP-based accelerator (serverspeeder or lotserver) provided by Appex > was deployed on my vps, and it was embedded into the kernel > supposedly. On the average it worked very well with eth0, but question > is it isn't very supportive with ocserv, because it cannot detect the > dynamical launch or destroy of the tun device perfectly. Then I add a > script (some limited function supported by serverspeeder) to force it > detect a new interface. On connect phase everything is ok, as I can > see, the script followed the "assigning tun device xxx". The key issue > comes to the disconnect phase that serverspeeder seems detect the > release of a tun device, once the client sends the disconnect message, > and then serverspeeder crashes(that seemed like a deadlock of > detecting the the released tun's communication). All of these > happened before my disconnect script execute a re-detect of all > interfaces. > I think the problem could lie on the sequence of the execution. To be honest I cannot really understand the issue here because serverspeeder is something unknown to me. However, it looks like it is not related to ocserv (if yes please clarify what is the issue), and as such I'd suggest to ask in some forum about serverspeeder. regards, Nikos
