[FreeNX-kNX] nxconnect released

[LROUFAIL at nc.rr.com]

Yes.  You are right.  Currently it does not support other ports.  It is a simple problem, I just haven't fixed it yet because I didn't need it!

I have revamped all the code and we will have it in cvs very soon.

- L

----- Original Message -----
From: Václav Šmilauer <smilauer at volny.cz>
Date: Tuesday, March 8, 2005 2:55 pm
Subject: Re: [FreeNX-kNX] nxconnect released

> Hi,
> 
> I have freenx server running behind firewall on tunneled ssh port 
> 2223. 
> My config reads <option key="Server port" value="2223" />, but 
> nxconnectsays:
> 
> READ: NX> 200 Connected to address: 213.151.??.??? on port: 22
> 
> (and connection fails). Apparently SettingsToParameters does not 
> processthat option. The original annoucement however says "It 
> supports 1.4.0
> encrypted sessions." which means ssh-tunneled (a.k.a. "Enable SSL
> encryption on all traffic" in !M nxclient). Or am I getting it wrong?
> 
> If source of nxconnect is released, I am willing to patch it so 
> that it
> works as expected.
> 
> Thanks for any help, 
> 
> Vaclav Smilauer
> _______________________________________________
> FreeNX-kNX mailing list
> FreeNX-kNX at kde.org
> https://mail.kde.org/mailman/listinfo/freenx-knx
>