+CLSTAT_PORT, +SRVMAIN_PORT#4
Conversation
client and srv cosmetic PORT changes, increased number of sockets, not sure why
this sets more static port range to use for client and server. you can switch that PortStart + PortEnd or change values for it was like more clear for people and actually, if they run it run from 1 host or network with NAT, then client and server should not use same port by any occasion - it may fail then/ you can think about it.
There was a problem hiding this comment.
actually you can't use the range of 0-1024 - it is binded for ftp/http/clock etc
but for client - sometimes it is more open and if it takes there, maybe it is wrong
now you can set the CLSTAT to 0 and for clients it will be random from this clPortRange
and for example set the range to hoger ports 63000-64000, but it's better to put that in GUI
with random switch and write some exact port, while leaving random port range more predefined.
it really produces error when server gets to random higher port, socket overload can be the problem of that
for example when they ask for heartbeat or server reply +socket runs and it may bump out the real server socket
|
yes, maybe the declarations should go to .h file, but it was in .c before and found there with hardcoded port numbers |
1 participant
client and srv cosmetic PORT changes,
increased number of sockets, not sure why
you can change/erase comments in file on your own
gtg