ChunkVNC with Rat's Perl Repeater - HELP!

[regi]

PLease help. I am confused over how to setup ChunkVNC with rat's repeater on my linux hosting provider.

Steps completed:
DONE. Perl repeater placed in CGI-BIN folder (on host)
DONE. Hosting provider has opened ports 5901 and 5500 (default ports for ChunkVNC)
DONE. Dyndns pointing to host IP
DONE. SSH enabled on host (to enable puTTY connection)
DONE. have used Rat's command to enable script:

Code: Select all

/home/**ACCOUNT NAME**/public_html/cgi-bin/ultravnc_repeater.pl -L BG -r -C -c 5901 -s 5501

Now when I compile ChunkVNC:
q. Do I set the WAN to the DynDns name?
q. Do I set the LAN to the hosting IP address? (because this is in fact a website WAN address, no?)
q. Do I set the server for 5500 or 5501? (if 5500 do I need to edit Rat's repeater code (above))?

Also I'm not sure if the kill command is correct

Code: Select all

pkill ultravnc_repeat

because when i use rat's command BEFORE AND AFTER killing the script

Code: Select all

netstat -anp --tcp | grep perl

I get the same message:

Code: Select all

(Not all processes could be identified, non-owned process info
 will not be shown, you would have to be root to see it all.)
tcp        0      0 0.0.0.0:5901                0.0.0.0:*                   LISTEN      416044/perl
tcp        0      0 0.0.0.0:5501                0.0.0.0:*                   LISTEN      416044/perl

[supercoe]

You'll have to ask Rat about the setup for his repeater, sorry I don't have experience with it.

You can set the WAN and LAN address to be the same.

You can compile the server to use whichever port you'd like but port 443 is required in order to have HTTP Proxy support.

[regi]

hi supercoe. thanks for the reply

q. do you mean I can set both the WAN and the LAN to the Dyndns address? ie. example.dyndns.biz
q. how do I contact Rat?

FYI - I was using a local LAN repeater (on my computer) until my internet service provider forced me to change my modem/router all-in-one. Now since I cannot loopback on the new device, I have to stack my old wireless router on top of this useless modem (which of course will not allow me to bridge)...therefore I'm getting an IP conflict (because my wireless router has a WAN that is actually a LAN!!!)

[supercoe]

You can set the WAN and LAN address to be the same.

Try posting in Rats thread to get a response from him: https://forum.ultravnc.net/viewtopic.php?f=50&t=17342

[regi]

okay will do.

just want to say THIS PROGRAM ROCKS! Thank you for all your hard work!!!!

...but I would recommend a bit more work on the program user-friendliness angle. This whole port nonsense is enough to drive the average user bananas, plus the documentation should be written so that a 10 year old can understand/install it

my 2cents

[supercoe]

Thanks, glad you like it.

Documentation is obviously difficult for me to write since I know the program in in out but I tried to make it as easy as possible.
I'm all ears if you have a better way to explain the setup especially the parts you find difficult to understand.

Keep in mind that "This whole port nonsense" is a trivial part of networking and can't be made any more simple without someone else running the repeater for you.

[regi]

yeah i understand. i don't mean to imply the port complications are your fault. porting should be a simple process, but invariably there's always a mystery issue that impedes the connectivity..whether router, firewall, program, or app....it's just a pain in the ass to solve.

BTW i am quite excited ny this Nat2Nat fork ur working on. When yoi've cracked that, all these porting issues will be history!

re: documention
i understand your dilemna. the problem is ur too smart and your audience is dumb. try to imagine me not seeing the difference b/w a modem or a router, or when you say "port" i think "ship"...
get my drift?

[supercoe]

I like the ship metaphor, I'll keep that in mind when writing documentation.

NAT2NAT is definitely the future and I'm equally excited about the software that Rudi was able to create.

[B]

regi, porting issues will NEVER be history, unless you like the idea of opening every port to the world on all PCs and inviting worms and other malware.

Even with NAT2NAT, a repeater/redirector/thingie needs to be listening on open ports. In testing thus far that has been through a single test server of Rudi's, but depending on a 3rd party goes entirely against the idea of controlling your own systems (not to mention it's difficult to scale) so I hope and expect that he releases that portion some day.

At which point you would STILL need to make sure that the thingie you're establishing is listening on at least one port!

If people insist on being ignorant of basic technology, then they will always be reliant on third party services (whether Google or Facebook or GoToMyPC or LogMeIn) to do the simplest things. A lot of people seem content with that... until the next outage or credit card dispute or arbitrary service termination.

[supercoe]

You always have a great way to put a spin on what I'm thinking.

ChunkVNC is a tool for technicians.
I wouldn't trust a mechanic to work on my car if they didn't understand how their tools function.
I'm not trying to be a jerk but I believe a basic understanding of networking should be required if you need a tool that helps you work on computers.

The reason I think that way is because of what B has explained, too much reliance on a third party service is a bad thing.

[regi]

B, I don't disagree with you....but the sad truth is that the product is USED by Users who likely do not have as much knowledge on the subject as yourself.
So do you want the user to have a frustrating can't figure this out experience with the product? Or an easy breezy WOW this is awesome experience? (why do you think Google makes so much $$)

Anyways, I'm not saying it's anybody's fault. It's just reality. I don't want to learn mechanics in order to be able to drive my car. Nor do I wish to become a networking technician in order to use a VNC. Rather, I just want to be a user who uses this product to help others with their computer questions.

but let's not digress this topic from the fact that ChunkVNC remains an awesome product that deserves high compliments: especially since you guys offer this product free AND continue to dedicate yourselves on making it BETTER

[B]

Okey doke. By the way, in the "it just works" camp, I highly recommend LogMeIn Free. I use it all the time.

So if you don't want to set up your own ChunkVNC/UltraVNC repeater (and the necessary port forwarding) you might look into that.

[regi]

will do thanks!