Repeater versions (win/linux) +downloads

Post by **Rudi De Vos** » 2005-10-08 21:35

Windows version mode I/II
Windows cersion mode SSL
Linux version

exe+md5sum and sourcecode

BSD license for the windows version is back GPL, needed because SSL is
implemented from GPL source.

http://sc.uvnc.com/index.php?section=27

superwopguy · Post by **superwopguy** » 2005-10-09 12:58

Can you please tell me how to increase the Max sessions of viewers and servers in the Windows source repeater. If I simply change the value of 20 in all instances to 200 will that work. Are there any other variables that are dependent on this number 20? For example in the Linux Repeater we must make sure that if we increase the Max sessions we must make sure that the following number is still bigger then the Max sessions. Please see Linux Repeater code below for example:

#define MAX_SESSIONS 100 //Maximum active repeater sessions

#define UNKNOWN_REPINFOIND 999 //Notice: This should always be bigger than MAX_SESSIONS

THank you for releasing the windows source code for the repeater.

superwopguy · Post by **superwopguy** » 2005-10-09 13:09

Just for everyone to know.

The Linux Repeater's download link does not work in the downloads section because there is an extra space after the last /

http://koti.mbnet.fi/jtko/uvncrepeater/

Just make sure to remove that blank space and you will be able to download the Lunix Repeater.

Post by **Rudi De Vos** » 2005-10-09 13:35

All files are also hosted on sourceforge and there mirrors
http://sourceforge.net/project/showfile ... p_id=63887

20 value...
1) A good connection require a minimum of 128k up/down ==256k
20 --> 5120k bandwidth --> this is already a 40MB line
200 --> 400MB
Unless you have a direct gigabit internet connection it does not make any sense changing the vlaue to 200.

The repeater at uvnc.com has a 10Mb backbone connection
(1250k up/down) --> we only can make 10-15 simultanious connections if all users use (zrle or tight compression)

You can nott simple change 20 to 200, 99 is used for error notofication

Jariko · Post by **Jariko** » 2005-10-09 22:28

Rudi De Vos wrote:All files are also hosted on sourceforge and there mirrors
http://sourceforge.net/project/showfile ... p_id=63887

The repeater at uvnc.com has a 10Mb backbone connection
(1250k up/down) --> we only can make 10-15 simultanious connections if all users use (zrle or tight compression)

You can nott simple change 20 to 200, 99 is used for error notofication

Yes, I agree (Oops, I stupidly wrote 200 to the html page also, maybe you could change it to 20

I originally changed these settings to #defines just because I dislike magic numbers (probably because my C teacher acted unpleasently if I used anything but 1 or 0 and #defines).

Now that these settings are #defines, it is easy to change them, but that does not mean it would really work with 100 simultaneous sessions, though

superwopguy · Post by **superwopguy** » 2005-10-11 15:59

I disagree, just because I want the option to have 200 workstations IDLE does not mean that I will be remote controlling 200 workstations simultaneously. I just want to be able to choose 1 workstation from 200 IDLE connections. This does not need 400MB connection. It will still be very usefull if you could please tell me how to change this value in the Windows Source Code. Thank you very much.

Post by **Rudi De Vos** » 2005-10-11 16:08

Then you also need add some keepalive to keep the tcp lines open.
Most router just close the connection after a certain idle time

superwopguy · Post by **superwopguy** » 2005-10-11 18:29

Doesn't your autoreconnect also keep alive the connection?

Post by **Rudi De Vos** » 2005-10-11 18:38

autoreconnect: reconnect after timeout

You better explain what you are actual trying to do..
i don't get the whole picture.

superwopguy · Post by **superwopguy** » 2005-10-11 19:36

Why would we need some keepalive feature if your application will automatically reconnect after time out. You specified before that we would need some keep alive for the tcp idle connections.

Rudi De Vos wrote:Then you also need add some keepalive to keep the tcp lines open.
Most router just close the connection after a certain idle time

But if the timeout is set to 5min and then after the 5min the application will automatically reconnect, there is no need for keepalive. It should always stay alive or refresh every 5min.

Rudi De Vos wrote:autoreconnect: reconnect after timeout

If I am wrong please forgive my ignorance. Thank you Rudi!!!