UltraVNC 1.3.9-dev1 - Download links

[Rudi De Vos]

Documentation
- https://www.uvnc.eu/download/1390/UltraVNC_SC_20.pdf
Test bins
Download
- https://www.uvnc.eu/download/1390/UltraVNC_139_dev1.zip
Source
- https://github.com/ultravnc/UltraVNC/re ... /1.3.9dev1

Changelog
-Added cloud connect
-SC based on latest full winvnc
-internal a lot of code changed, some cleanup was needed

The menu has a new entry "Cloud connect"



Cloud connect windows


The viewer also has the new option "Cloud"


The server code is calculated.
Both server and viewer need to reffer to the same cloud server.
To connect, enter the server code on the viser site.

led (orange) = cloud server found
led (green) = viewer and server found each other, viewer can press connect






UltraVNC SC
UltraVNC sc now use the same code as UltraVNC.
Both plugin and ddengine dll's are buildin, no need for the extern dll's.



Helpdesk.txt has been modified, see sample for each type of connection

[Sainsuper]

Hi Rudi, thanks for your work.
What is difference between repeater and cloud server and how it works? code is manage from cloud server? users will use personal cloud server?
sorry for many questions?

[Rudi De Vos]

Difference is that a cloud server is only used to initiate a session, ( a few 32bit packets)
reapetaer ->tcp
cloud -> udp
A cloud server can easy serve a few 1000 connections while a repeater is limited to his bandwidth.
There wil be a cloud server you can host, current cloud.uvnc.com can be used to test.

There is some drawback.
In the current implementation the cloud component act as a udp layer, it's slower then direct tcp.
The natrouter need to support the direct udp rendezvous protocol.

When a server is announced he is visble for 60s and the server announce himself every 60s.
This mean that the server will still show as online for 60s after you close it.

[SkyBeam]

Thanks for the update and new feature. I will definitely test it. A few questions/comments though:

• Will the cloud component be available in source code? Specifically a Linux version would be preferred. (at least by me)
• Is the connect code going to be "stable" or changing randomly and on each connection? Random might be better for privacy while persistent codes might be useful in many other scenarios.
• Is there a fallback using cloud as a relay in case no NAT traversal is going to work? Perhaps with options to enable/disable it depending if you run a public server and don't want it to relay the traffic.
• Can the cloud connect dialog be opened via command-line or API? Would be handy to allow opening an info-dialog showing the connect code rather than right-click on the icon and select cloud connect. Also if the tray icon is hidden. Also an option to open the cloud connect info dialog rather than properties by default (double-click on the tray icon) might be handy.
• I guess cloud connect and repeater mode can be used in parallel, right? So UVNC connecting to a repeater but still allowing cloud connect should be possible (perhaps as a fallback for non-working NAT traversal (see above).

[Rudi De Vos]

Will the cloud component be available in source code? Specifically a Linux version would be preferred. (at least by me)
-win32 code yes
-It's a small code, i can not port it to linux myself.

Is the connect code going to be "stable" or changing randomly and on each connection? Random might be better for privacy while persistent codes might be useful in many other scenarios.
We use the udt library rendezvous protocol.

https://sourceforge.net/p/udt/git/ci/master/tree/

Is there a fallback using cloud as a relay in case no NAT traversal is going to work? Perhaps with options to enable/disable it depending if you run a public server and don't want it to relay the traffic.
You can activate all protocols, but how to detect if one is working and auto switch is harder.


Can the cloud connect dialog be opened via command-line or API? Would be handy to allow opening an info-dialog showing the connect code rather than right-click on the icon and select cloud connect. Also if the tray icon is hidden. Also an option to open the cloud connect info dialog rather than properties by default (double-click on the tray icon) might be handy.
winvnc -cloudserver ip direct opens the dialogbox, also see SC settings.

I guess cloud connect and repeater mode can be used in parallel, right? So UVNC connecting to a repeater but still allowing cloud connect should be possible (perhaps as a fallback for non-working NAT traversal (see above).
Not tested: cloud connect run in an other thread and should run simultanious

[lwc]

This is very cool!

I suggest to fix the words to encryption and double though:


I wouldn't mind submitting a pull request, but the new version (at least when it comes to SC) is missing from GitHub, i.e. it's closed source.
Please see https://github.com/ultravnc/SC/issues/3.

[Rudi De Vos]

SC source is the same as winvnc source
See tags, they reffer to the same source.
https://github.com/ultravnc/UltraVNC/re ... SC_20_dev1
https://github.com/ultravnc/UltraVNC/re ... /1.3.9dev1

Typo's updated

build

[Rudi De Vos]

Extra info
https://github.com/ultravnc/SC/issues/1

[stefanorossetti]

Hi Rudy, I'm doing some tests with the new version you are developing.
this happens on some PCs
cloud connect code = 0000000000

question1 = in the final version will the cloud code always remain the same?
question2 = you will be able to create your own private cloud.connect.serer server

request:
it would be possible to pass the code to a windows variable so that with an external batch I can then view it in my app ....

Thank you

[Rudi De Vos]

cloud connect code: it just some numbers from the mac address, as long as your netywork card stay the same the number is the same.
0000000000 -> looks like the function used to extract the mac fail

own server: yes

Code:
-some copy/paste function is needed
-variable, should be possible, good idea

[stefanorossetti]

hi Rudy, sorry for my english
for the cloud code I noticed that if the pc has two network cards (a lan and a wifi usb) winvnc always returns cloud code 0000000
Tested on two PCs and the result is the same.
If the pc has only one physical and one virtual LAN for vpn connections, there are no problems.

hope this will help for development.

Thank you

[Akrat]

SC 2.0 1.3.8 and 1.3.9 seem to do away with the ability to call the EXE with the -connect parameter and is dependant upon using the helpdesk.txt file for the connection information. I really appreciate the renewed development to update the project but these changes will prevent me from using the newer versions.

Just some input, I'm fine with using the old stuff.