Dispatcher / Repeater

[hallipr]

Has the SC source been updated with the changes made to the main WinVNC source, or is there no need to bring those changes over to the SC side?

I am a VB/C# developer just starting to work with C++, and I may be a bit optimistic in my programming abilities. I would like to modify the repeater to function as more of a dispatcher, if it determines that a viewer is accessible by direct connection by a SC server.

Possibly, both the server and the viewer choose a port, or random port from a range, as their inbound port, with uPNP support. They also pick a session ID to be matched to the appropriate party on the repeater. When they connect to the repeater, the repeater tries to make a reverse connection on the inbound port designated by the viewer/server. If a direct server -> viewer connection is possible, then the repeater just instructs the server to connect to the viewers IP & port. If the viewer is behind a firewall and the port is not open, then the repeater would try the same thing on the server side, attempting to pair up a viewer -> server connection. If that also fails, then it reverts back to a standard Viewer -> Repeater <- Server connection.

Does this sound possible? To ambitious?

[JDaus]

to me, this sounds feasible, and quite a good idea.

there are ways of doing nat-to-nat, but they add a fair amount of bulk to the app.

what your suggesting sounds realistic and should be achievable

I would start by making a separate app that connects to the repeater, then mod both to do what you want ... if it all works well, then look at integrating in uvnc ...

the sc source hasn't been updated in years, we a working on getting same (or similar) functionality into the server code. this w
y, one code base can be maintained that does sc & server ... much simpler maintenance ...