Re: DAST: Multicast Beacon - pansio@crc.u-strasbg.fr


Hi, Jean-Jacques -- We're looking at this right now, and will see if this
can be worked into the latest version of the Beacon which we're hoping to
release in the next few weeks.

Thanks for the headsup!

Mitch



At 08:25 AM 2/11/2005 -0600, Apache wrote:
> 
> Contacting DAST re: Bug report about Multicast Beacon
> From: Jean-Jacques Pansiot <pansio@crc.u-strasbg.fr>
> 
> Question/Comment:
> This concerns a bug in the multicast beacon V1.1-0.
> When running the beacon with the default address 233.4.200.19, it appears
that
> most RTCP reports are fragmented. This is because the parameter
> #define RTP_MAX_PACKET_LEN 1500
> is too high : this generates IP packets of size 
> 1500 + 8 (UDP header) + 20 (IP header) which is too big for most
interface MTU.
> In fact these packets are fragmented by the sender.
> This can cause problems because IP fragments are not always correctly
treated
> by firewalls. For example for some beacons I receive only the first
fragment of each packet, making these beacon info unusable.
> 
> Hope this can help
> 
> 
> Jean-Jacques Pansiot
> 
> 
--
Mitch Kutzko | mitch@dast.nlanr.net | mitch@ncsa.uiuc.edu | 217-333-1199
http://hobbes.ncsa.uiuc.edu/



Other Mailing lists | Author Index | Date Index | Subject Index | Thread Index