Streamerp2p Forum

Hi Guys.

Posted here to confine knoledge to streamer testers and trustee's only

Some time ago I noticed some listeners connected directly to my broadcast source IP address, who had apparently defined "UDP p2p (in use)" to a value of port 0.

according to RFC 1700 a reserved port.
http://www.faqs.org/rfcs/rfc1700.html

Allow in its self use of port 0 is not a volation

I have done research that indicates that when a streamer listener defines port 0 that they are able to tune into a broadcast but no other clients are able to connect to them and form an onward chain|tree.
I beleave this acures because many manifcatures of hardware and software firewalls have inadvertantly writen application firmware & software which permits incoming packets on this port, but blocks all outgoing packets

regards Double Q

Hi QQ,
1.47H? Do you still use a release candidate? Ok 1.47 and 1.47h are the same but it's better to use the "official" version number

The port zero problem isn't new:
http://www.streamerp2p.com/forum/viewtopic.php?t=1783
http://www.streamerp2p.com/forum/viewtopic.php?t=1786#6682

I can enter port zero for TCP audio but not for UDP p2p.

Sends to port 0 is a bug, not sure how the send function gets to the actual sending part with port being 0, I've already fixed it to not actually send in 1.48.
Fixed TCP to not accept port 0 now.

thanks chief streamer dude