Expand my Community achievements bar.

SOLVED

How to configure a port range for RTMP

Avatar

Level 1
I’m using Flex version 2 on Windows XP. I’ve
created a test that opens a connection over RTMP. The server
accepts connections on port 2037 and then seems to spawn a new
connection for each client on a different port.

After server startup Netstat shows the connection below
(ns02dt00223 is the network name of my laptop):



TCP ns02dt00223:2037 ns02dt00223:0 LISTENING



Then after starting a publisher on the topic and sending a
message:\



TCP ns02dt00223:2037 ns02dt00223:0 LISTENING

TCP ns02dt00223:1696 localhost:2037 ESTABLISHED

TCP ns02dt00223:2037 localhost:1696 ESTABLISHED



And after starting a listener on the topic:



TCP ns02dt00223:2037 ns02dt00223:0 LISTENING

TCP ns02dt00223:1696 localhost:2037 ESTABLISHED

TCP ns02dt00223:1720 localhost:2037 ESTABLISHED

TCP ns02dt00223:2037 localhost:1696 ESTABLISHED

TCP ns02dt00223:2037 localhost:1720 ESTABLISHED



My question is: is there some way to configure the range of
ports used for connections?

1 Accepted Solution

Avatar

Correct answer by
Former Community Member
I believe this is expected and is simply how TCP works to
assign source ports

and destination ports.




http://en.wikipedia.org/wiki/TCP_and_UDP_port





View solution in original post

2 Replies

Avatar

Correct answer by
Former Community Member
I believe this is expected and is simply how TCP works to
assign source ports

and destination ports.




http://en.wikipedia.org/wiki/TCP_and_UDP_port





Avatar

Level 1
Hi Peter, I think you're right. The problem is that in our
case client and server are in separate networks. In between is a
router that doesn't understand networking very well.

Thanks for the link, I'll use it as ammunition in my
discussion with our security officer.
The following has evaluated to null or missing: ==> liqladmin("SELECT id, value FROM metrics WHERE id = 'net_accepted_solutions' and user.id = '${acceptedAnswer.author.id}'").data.items [in template "analytics-container" at line 83, column 41] ---- Tip: It's the step after the last dot that caused this error, not those before it. ---- Tip: If the failing expression is known to be legally refer to something that's sometimes null or missing, either specify a default value like myOptionalVar!myDefault, or use <#if myOptionalVar??>when-present<#else>when-missing. (These only cover the last step of the expression; to cover the whole expression, use parenthesis: (myOptionalVar.foo)!myDefault, (myOptionalVar.foo)?? ---- ---- FTL stack trace ("~" means nesting-related): - Failed at: #assign answerAuthorNetSolutions = li... [in template "analytics-container" at line 83, column 5] ----