20 Jan
2016
20 Jan
'16
4:34 p.m.
On 2016-01-20 16:17, Robert Armstrong wrote:
Yes. Sorry.
Not sure how
you meant the two lines above to be read. How could a passive
connection use the same port as a passive one?
I think you misspoke and used the word "passive" twice in error, right?
For active connections, the /PORT is the port
number to connect to on the remote end. The local port number is moot and is assigned
dynamically.
Aha! That is interesting. So Multinet do not control the local port
number when in active mode. Does that mean it also accepts connections
from anywhere for passive connections? Or how do they authenticate?
IP address only?
For passive connections, the /PORT is the port
number to listen to on the local host.
QED - you can have as many outgoing active connections as you like, and exactly one
incoming connection all on the same port. But if you have more than one listener on the
local host, then they have to listen to unique ports.
Now I understand how you meant it. I'm thinking local machine all the
time, and all connections will have different local ports then. What
remote port is used is also a different domain.
TCP can listen for, and accept multiple connections on one port. telnet
is a typical example of this, as well as http. So I was wondering if
Multinet also did that, but apparently not then. Thanks.
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol