More questions on repeater

[IlikeUVNC]

Hi there,

I have been using SCIII for quite a while with success.
Reading everything about PHW convinced me to at least start a trial on it.

So I followed all instructions (great THANK YOU to bevtech and redge).
And another BIG BIG appreciation to Rudi !!!

Repeater Setup
------------------
I copied the repeater (the one coming with the PHW distribution) to a new folder and started it with the default settings.
This all on the same server Iused the UVNC repeater before. For sure I disabled this old version

Viewer Setup on my local PC
---------------------------------
For viewer configuration I selected the option "Via Repeater" and the following parameters:
Alias: FirstTry
Password: 123456
Use Https proxy
ID 123456
Host Repeater: <Repeater's IP-address>
Listen Port Viewer: 443
Listen Port Server: 443
UPnP: Do not use Auto Map

After saving the settings I created the server with the options to let the user enter password and ID.


When starting server I get the following log:
Start
(none)
relay_method=HTTP(3)
relay_host=proxy
relay_port=8080
relay_user=<my NT-username>
local_type=socket
local_port=1111
dest_host=<Repeater IP address>
dest_port=443
not matched, addr to be SOCKSified: <Repeater IP address>
resolving host by name: proxy
resolved: proxy (10.49.40.22)
connection to 10.49.40.22:8080
begin http_relay()

<long break>

http proxy is not allowed.
Using Repeater
<Repeater IP address>
ID:123456
Failed to connect
A connection attempt failed because the connected party did... "can not read more here"
Init Network failed

When starting viewer I get the following log:
(none)
relay_method=HTTP(3)
relay_host=proxy
relay_port=8080
relay_user=<my NT-username>
local_type=socket
local_port=1111
dest_host=<Repeater IP address>
dest_port=443
not matched, addr to be SOCKSified: <Repeater IP address>
resolving host by name: proxy
resolved: proxy (10.49.40.22)
connection to 10.49.40.22:8080
begin http_relay()

<long break>

http proxy is not allowed.
Using Repeater
<Repeater IP address>
ID:123456
Failed to connect
A connection attempt failed because the connected party did... "can not read more here"
Network stopped, closing viewer

The repeater log shows no activity at all.

Going back to SCIII and "old" repeater everything works fine with same settings on my local PC firewall etc.

Question:
Does PHW really use port 443 (SSL) ?
Anything else I didn't take into consideration ?

Any help or hint is very much appreciated.

Thanks,
Werner

[Rudi De Vos]

For me it works using uvnc.com and the proxy of my isp (netapp cache)

SCIII
server (SSL client) <-proxy-->443(SSL server)repeater
viewer (SSL client) <-proxy-->443(SSL server)repeater
The repeater unencrypt/decrypt the data and cross it between server and viewer
(You have 2 seperate encryptions,repeater need to encrypt/decrypt)

PHW
server (buildin encryption) <-proxy-->443 repeater
viewer (buildin encryption) <-proxy-->443 repeater
The repeater cross the encrypted data
( The repeater does not know the data, encryption is fully done between
server and viewer)


If you have a proxy that can see the difference between SSL and twofish
encryption and only allow pure SSL it will not work.

[bevtech]

Nothing can share port 443 on that repeater pc..

I would try using the default ports and see how that works
then try other ones. I would not set the viewer and server to the same port ( especially 443)

But if you are dealing with proxies you might not have a choice but to use port 443.


Try the default just to see if it will work maybe the repeater just isnt functioning properly if it works with default ports then you will at least know that it is installed and configured properly.

[IlikeUVNC]

If you have a proxy that can see the difference between SSL and twofish
encryption and only allow pure SSL it will not work.

Hi Rudi,

I'm pleased about your professional and founded reply.
I'm affraid the limitation you described does most likely hit the point.
In our company all SSL connections get opened and analyzed regarding pure SSL.
Since UVNC SCIII uses pure SSL it was and stil is working.

I will see if I can use another port to reach repeater from our company.
But there are not many ports left open to setup connections to the internet.
I guess other companies will do the same if they didn't allready.

Are there any plans to use pure SSL again ?

Thanks and keep on doing this great job
Werner

[redge]

dynhost repeater fail.
started phw_viewer and test dynalias "choucroute"

1st test
Repeater test:
External ip: < (????)
Local ip: 192.168.1.30

2nd test not change dynalias "choucroute".
Repeater test:
External ip: 192.168.1.30 <--- (should not possible !!!)
Local ip: 192.168.1.30