MAC Client

[quantex]

I would like to know if it possible to configure the mac client with the server ip inside.
Right now we have to configure the ip adress in server.txt but i would like to know if it's possible to configure in InstantSupport.sh

One more question, is it possible to configure mac client to automatic connect?

Thanks in advance
Regards

[supercoe]

I've been neglecting the Mac InstantSupport for awhile but these features are planned. Since demand seems higher now for Mac support I'll see if I can get this implemented for the next release.

[quantex]

Thanks, i'm looking foward to see this changes implemented.

Thanks once again.

[kwhite]

It's very easy to do, although you will need access to a mac *cough*or VirtualBox*cough*.

Follow the compliation instructions included with the src.zip in the OSX folder, except edit the InstantSupport.sh script with a text editor (TextEdit seems like a reasonable choice).

Comment out the export server_host=$(cat ... line by putting a pound sign (#) in front of it. This is the line that loads the server.txt, and my guess would be that it'd error out or something if the file is missing.

At this point you could either add a line specifying the server_host variable (something like server_host=my.server.com:5500), or personally I see no need and just edit the line that sets connect_str replacing $server_host in the line with your server address (including port). Something along the lines of connect_str="-connect repeater://my.server.com:5500+ID:$idnumber"

HTH =)

[B]

kwhite, I just want to thank you for being a well spoken, on point, and helpful first-time poster. It's very refreshing!

(I have no idea if your suggestion is accurate, but that's beside the point. 99.742% of the time, a first-time poster resurrecting a 6 month old thread is a blubbering weasel spammer.)

[aselby]

I was looking for the OSX source to compile and maybe a little more pointers ?

I was kinda hoping to use this a support tool for our laptop crew ... we have about 40 laptops that trail around everyone and really only come to the office once a year. There are about 15 macs, I would like to install this and leave it installed and use it like logmein, have them install it then tell me the code I will right it down then connect to them whenever and wherever they are when they need help ?

This seems like it should work and it be great if I could use it with macs too

[B]

The source code should already be in the distribution. I believe it's just a wrapper/package around x11vnc.

You might also check out GITSO for cross platform support. It's still my "go-to" app, though lately I've been impressed with the free join.me service.

[aselby]

I've look at folder chuck created and I don't see anything called x11vnc do I need to download the source for uvnc ?

[B]

No, it really has hardly anything to do with UltraVNC, other than supporting the repeater. Again, he just wrote a little wrapper around x11vnc; the script code was there the last time I looked, which is how I realized he was using x11vnc.

Oh, and if it's not in the current release, check out the previous ones. As he said, the Mac stuff has lagged behind.

[supercoe]

Yea it's been gone since release 3.3 as it wasn't really that great and it doesn't work in the new OSX.
The source code is in the older releases and I can share a link to get it if you want but I doubt it will be helpful.

Change Log 3.3:
Removed Mac InstantSupport. *Hasn't worked since OSX 10.5, hopefully will come back soon!

[B]

Hint -- OSXVNC has released its initial OSX Cowardly Lion support. Bundle that with the secret NAT2NAT Reloaded technology, and Bob's your uncle!

[supercoe]

You're such a dreamer.

[B]

UDT Tutorial
Firewall Traversing with UDT

While UDT was originally written for extremely high speed data transfer, there are many other potential benefits from this reliable UDP-based library. One particular usage is to setup reliable connections between machines behind firewalls. To meet this requirement, UDT has added the rendezvous connection setup support.

Traditional BSD socket setup process requires explicit server side and client side. To punch NAT firewalls, a common method is to use the SO_REUSEADDR socket option to open two sockets bound to the same port, one listens and the other connects. UDT provides the more convenient rendezvous connection setup, in which there is no server or client, and two users can connect to each other directly.

With UDT, all sockets within one process can be bound to the same UDP port (but at most one listening socket on the same port is allowed). This is also helpful for system administrators to open a specific UDP port for all UDT traffic.

Example: Rendezvous connection setup. (Note that there is no need to set UDT_REUSEADDR here because it is true by default.)
UDTSOCKET u;
...

bool rendezvous = true;
UDT::setsockopt(u, 0, UDT_RENDEZVOUS, &rendezvous, sizeof(bool));
UDT::bind(u, &known_addr, sizeof(known_addr));
UDT::connect(u, &peer_addr, sizeof(peer_addr));

In addition, UDT also allows to bind on an existing UDP socket. This is useful in two situations. First, sometimes the application must send packet to a name server in order to obtain its address (for example, this is true when behind an NAT firewall). Users may create a UDP socket and send some UDP packets to the name server to obtain the binding address. Then the UDP socket can be used directly for UDT (see bind) so that the application does not need to close the UDP socket and open a new UDT socket on the same address again.

Second, some firewalls working on local system may change the port mapping or close the "hole" is the punching UDP socket is closed, thus a new UDT socket on the same address will not be able to traverse the firewall. In this situation, binding the UDT socket on the existing UDP socket is not only convenient but necessary.

...

UDT source code
./app: Example programs
./doc: UDT documentation (HTML)
./win: Visual C++ project files for the Windows version of UDT


To make:
make -e os=XXX arch=YYY

XXX: [LINUX(default), BSD, OSX]
YYY: [IA32(default), POWERPC, IA64, AMD64]

For example, on OS X, you may need to do "make -e os=OSX arch=POWERPC";
on 32-bit i386 Linux system, simply use "make".

On Windows systems, use the Visual C++ project files in ./win directory.

(The technology in NAT2NAT Reloaded is multiplatform.)

Clearly what we need is to clone Rudi.

Edit: Just stumbled over Karl's mention of alternate NAT-penetrating method http://samy.pl/pwnat/ and his own preliminary webserver-based "NAT2NAT" handshake code at http://www.karlrunge.com/x11vnc/vncxfer

[B]

Also just noticed that x11vnc just MIGHT support OSX Cowardly Lion now (so you could go back to the previous script wrapper).

He doesn't exactly come out and say it, but it's strongly implied that 0.9.13 and 0.9.14 fit the bill.

http://www.karlrunge.com/x11vnc/