3 Replies Latest reply on Jun 4, 2014 10:46 AM by Michael Thornburgh

    Why do Flash clients still use high ports in 50-60K range for RTMFP p2p streams, even if Adapter.xml changed to 19350-19399?

    FransMaas1952

      We configured Adapter.xml like this:

       

      <HostPort public="46.22.183.164:19350-19399">46.22.183.164:19350-19399</HostPort>

       

      We were assuming that this would than also affect the ports used by the respective Flash clients in the peer-to-peer comms.

      We were hoping to be able to than close firewalls accordingly, giving a feeling of more security.

      But we still see clients using ports in the 50-60K range, like: 58341, 60346, etc.

      P2P is then not established, and our fallback scenario kicks in.

       

      We found this in the Admin manual for Adobe Media Server:

       

      19350-65535RTMFPUDP

      By default, clients use port 1935 and ports 19350-65535 to communicate with Flash Media Server over the RTMFP protocol. The RTMFP protocol communicates over UDP. Clients connect to the server over 1935 and the server redirects the client to a port between 19350 and 65535.

       

      Allow inbound UDP traffic on 1935 and outbound traffic on ports 19350 - 65535.

       

      Allowing UDP inbound traffic from unknown hosts on ports 19350 - 65535 is optional. Flash Media Server sends a packet out to a new client to redirect it to a port in the range 19350 - 65535. This packet attempts to punch a hole to allow the client traffic back in over the correct port.To use server-side RTMFP NetConnections, allow outbound UDP traffic on all ports.

       

      We had hoped/assumed that after changing Adapter.xml we would also be able to use the lowered upperbound in firewall config.

      But apparently this is not the way it works.

       

      Did we overlook something? Is it working as designed? Or is there another way to configure the ports used by the Flash clients.

       

      Regards,

      Frans Maas