Re: [tcpdump-workers] libpcap and select problem

2004-10-27 Thread Ying Li
> The other weird thing is that the overall transfer > time of a bulk of data is 50%+ faster with these > timeout problems, as opposed to setting a longer > timeout or taking out the select()(i.e. server > sends, > waits, sends, assuming no packet lost) ops, ignore this part, i figured out why

Re: [tcpdump-workers] libpcap and select problem

2004-10-26 Thread Ying Li
time out as in retval = 0 OS = redhat 9 I used ethereal to monitor traffic. my server is suppose to send something to the client using raw socket, use select/pselect with pcap to wait for reply or resend last packet if timeout (retval =0). I reset(like putting tv_sec=0;tv_usec=1500; before select)

Re: [tcpdump-workers] libpcap and select problem

2004-10-25 Thread Guy Harris
On Oct 25, 2004, at 1:27 PM, Ying Li wrote: Sometimes select() times out way too fast, like 0.0001 seconds while my timevar is set to 0.001 sec. "Times out" in the sense that "retval" is 0? On what OS are you doing this? - This is the tcpdump-workers list. Visit https://lists.sandelman.ca/ to unsub

[tcpdump-workers] libpcap and select problem

2004-10-25 Thread Ying Li
Hi, I'm trying to write a program that simulates a RDP (RUDP) protocol with a timeout on the host. Right now i have it as -pcap_setnonblock(...) -reset timevar -retval = select(, &timevar); or pselect(...) -if(retval) pcap_dispatch(...) or pcap_next_ex(...) -else timeout++ I've