by 
, (6825 days ago)
When can I call findMtu? And when can I set it?
I suppose
- wodVPNcom.connect
- OnConnected
wodVPNcom.FindMTU(10)
- OnFindMTUDone
wodVPNcom.MTU := xx
Thanks
Correct way would be, in my opinion, on IDLE connection (this is very important!) to send packets, starting with 2000 bytes (as example), and send them out. As long as it fails, lower them 50 (to 1000, 500, 250...), and when it starts working increase them 50 .
I think we should add that on wodVPN internally.. Can you wait 2-3 days so auto-mtu-discovery is implemented?
Kreso
Yes, it would be fine!
Thanks a lot
Valter,
can you download wodVPN again and try it out? Call FindMTU (argument can be 0) and wait up to 10 seconds.
Check for FindMTUDone - it should contain MTU. You can decrease it by 4 to put to MTU property.
Kreso
by , (6825 days ago) @ Jasmine
Hi Kreso,
the method seems to work fine. It discover the correct MTU in few seconds ... good job!
PS: I'm sorry to say that unluckely that doesn't resolve my RDP crashes. RDP seems to be stable with an MTU of 1350 (findMTU reports, correctly, 1472), but copy/paste of files works at 40Kb. My ADSL is 2048/256.
PSPS: why -4? wodvpn don't needs 20 bytes?
Brilliant, even works on the mobile phone...
Not only wodSFTPdll is excellent, the service you have provided is outstanding and second to none!
Congratulations on an excellent product and first rate support!
Congratulations on an excellent product and first rate support!
The wodCrypt product is great and we appreciate your effort to add support for UNIX Crypt.
Thank you very much for the rapid responses. I was a little nervous about dealing with a company that is on a different continent from me. You have proven my concerns to be unfounded.
Thank you very much for the rapid responses. I was a little nervous about dealing with a company that is on a different continent from me. You have proven my concerns to be unfounded.
May I say how nice it is to work with components so complete and self-explanatory that using them in my application is as instinctive as though I wrote them myself?
Your .NET components allow us to blend .NET technology seamlessly with secure communication, and with excellent technical support.
I can only hope I will have the pleasure to work with other products by "We Only Do" in the future.