How sure are you, when you say the OS drops packets ??
Did you use a sniffer to verify it ??
You can easyly trace down if there is a packet drop by using "netstat" with -s option.
But the tricky part with UDP is you cannot send large packets (If i recall it correctly, 1470 on Win2k server)
So, your data might get fragmented. Again the packets may not arrive in teh same sequence as you sent.
I guess for secure UDP (I dont see many people work on secure UDP though) this might be a problem.
I'd say you should investigate a little more on where exactly the packets are lost. Errors could happen even at athe cleint side. BTW, are you getting any errors on *any* of your sendto()s and recvfrom()s ???
~ J
Main Topics
Browse All Topics





by: _nn_Posted on 2003-10-20 at 14:00:45ID: 9586346
Well, you could try to increase the buffer sizes by calling setsockopt() library/de fault.asp? url=/libra ry/ en-us/w insock/win sock/setso ckopt_2.as p
http://msdn.microsoft.com/
Tune the values for SO_RCVBUF and SO_SNDBUF. This way you'll make sure that it's indeed the culprit... or maybe not. There are possibly many other reasons why the connection could be unreliable. If tuning the sizes of the buffers doesn't help, and if other network programs (file sharing for instance) works ok between the boxes, you'll have to question your program design.