Link to home
Start Free TrialLog in
Avatar of mehranalmasi
mehranalmasi

asked on

Buffer ethernet packets

Hello Experts.

Using IP network and proprietary hardware, we have created a network with two nodes. one streams out video and the other one receives and processes it. There is no way to control how fast the sending node sends its stream as it does so at a steady rate. The receiver however falls behind at times and can not keep up with incoming stream.

The question is what is the best way to synchronize the two so no packets are lost. The solution has to be something like a  switch in between the two that buffers data when the receing node falls behind. if I am correct there has to be some communication between the receiving node and the buffer to communicate send and receive flags.

would Broadcom's BCM5315 5-Port 10/100 Switch with on-chip packet buffer would do this?


thank you.
Avatar of pgm554
pgm554
Flag of United States of America image

No,the receiving has to do with the way that the TCP stack is configured.Bumping it up to 128K is a possible solution.

For W2K see:

http://rdweb.cns.vt.edu/public/notes/win2k-tcpip.htm

otherwise try:

http://www.psc.edu/networking/projects/tcptune/
Avatar of mehranalmasi
mehranalmasi

ASKER

pgm554,
thanks for the links. If bumping up the buffer on the receiver is not good enough, does that mean that we have to come up with something like Tivo in the middle for buffering more data? Meaning writing overloading packets to a hard disk.
ASKER CERTIFIED SOLUTION
Avatar of pgm554
pgm554
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
There could be a number of reasons for slow response on the receive side.  For starters:
1.  Errors on the link (causing retransmits and data to arrive out of sequence)
2.  Not enough bandwidth or misconfigured interface (transmitter may still send it but it never enters the physical pipe and drops, depending on your hardware, you may never see an error from this)
3.  Congestion in the network (you haven't really described how they are linked)