Re: [Fwd: Re: [Zinf-devel] speaking of rtp://]

Hi,

	This was me.............

	I contacted the author of Obsequiem, and just was thrown for a
loop about multicasting.

> > 
> > the pseudo-url format rtp://address:port works only where address is 
> > the destination address of the packets,
> > specifically zinf was coded for this to be a multicast address. 
>
	Ok. I'm not familiar with multicast.
>
> > for 
> > example rtp://233.64.133.10:7000 would tune into the multicast stream 
> > at that multicast address/port.
>
	I was told that the address would be something with 224.X.X.X. .
>
> >  it could work with unicast by 
> > specifying my own ip as the address, but this is not very common
> > 
> > so the solution is to make sure that obsequium is actually sourcing rtp 
> > multicast,
>
	Ok, HOW?
>
>
> > then change the rtp:// url you pass to zinf to match the multicast 
> > group/port
> > 
>
	Ok, HOW?  
>
> > if you do this, you should see IGMP reports with TCPdump, and if 
> > multicast is working properly you will see the packets flow, src ip of 
> > the server, dst ip of the multicast group.
> > 
>
	I tried, I didn't see anything.



		Tuc/TTSG Internet Services, Inc.


-------------------------------------------------------
This SF.NET email is sponsored by: Order your Holiday Geek Presents Now!
Green Lasers, Hip Geek T-Shirts, Remote Control Tanks, Caffeinated Soap,
MP3 Players,  XBox Games,  Flying Saucers,  WebCams,  Smart Putty.
T H I N K G E E K . C O M       http://www.thinkgeek.com/sf/