Siddharth Srivastava wrote:
> let me describe my problem.....
>
> i an using sendto() to transfer some audio data across the n/w.The actual
> transmission is scheduled using gettimeofday() and rate of the audio,
> whaence it calls a function which packetizes the data and sends it using
> sendto().The problem is that the clients across the n/w are not able to
> recv the data, while if i have a client on the local machine(the one which
> the server is running),the reciept is perfect.
> My interpretation of the problem is that it can be because the network is
> slow.Can this be the reason??.Or maybe there is a bug in the way i am
> assigning the fields of the "to" arg of sendto.
> The question is:
> 1) can/does the speed/load on the network determine the way the UDP
> packets are treated??
In what sense? If there is an intermediate router, it is free to
discard packets if its input queue is full.
> 2) can the "to" argument be buggy in a way that it works on the local
> machine transactions but not across the n/w??
It's possible to specify the wrong IP address (e.g. forgetting to use
htonl() when necessary).
One distinction between sending a UDP packet via loopback and sending
it via some other interface is the MTU (the loopback MTU is usually
larger than ethernet, PPP etc). If your packets are larger than the
MTU, things will probably go wrong (IIRC, sendto() should fail with
EMSGSIZE).
--
Glynn Clements <[EMAIL PROTECTED]>
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
