[FreeNX-kNX] kNX behind a firewall (only port 22 open) unusable?

[LROUFAIL at nc.rr.com]

Ok, I think I see the problem.  I had not tested with FreeNX server before.  I have just set one up so I will verify tonight when I am home from work.

When it sends the client version info, it expects a 134 back (Protocol accepted) to move onto the next step.

Looking at the FreeNX code, it sends the 134 anytime it sees 'hello' or 'HELLO' from the client.  

Unfortunately, I send 'Hello'.  It will be a very quick change and hopefully I can make it tonight.

In the meantime, you could edit nxserver (it is just a shell script) and see if you get any further.  Where you see 'hello*|HELLO*)' you can change to 'hello*|HELLO*|Hello*)'

- L

----- Original Message -----
From: Tomasz Chmielewski <mangoo at interia.pl>
Date: Monday, February 21, 2005 4:31 am
Subject: Re: [FreeNX-kNX] kNX behind a firewall (only port 22 open) unusable?

> LROUFAIL at nc.rr.com wrote:
> > It looks it installs and runs fine.
> > 
> > based on the output it looks like you just need to add the 
> password to your config file.  It should fail a lot more 
> gracefully than it does!
> > 
> > Maybe I will work on that for the next version.  Also, now 
> nomachine has released the encryption routine they use in the 
> config file, so someone could create a patch to use the config 
> file without modifications.
> > 
> > These instructions are on the website:
> > 
> > There are a couple of changes you have to make to the 
> configuration file to make it work. I could not get the NX Client 
> to generate the password that the server expects, so I had to 
> create the nxpassgen utility to generate it. Just execute the 
> utility. It will ask for the NX username and password. In the 
> configuration file, in the Login group, add an entry for the 
> password. It should look like this:
> > 
> > <group name="Login" >
> >    <option key="Password" value="password from nxpassgen" />
> >    <option key="User" value="the user" />
> > </group>
> > 
> > Try that and let me know if it helps.
> 
> All right. I had:
> 
> <option key="Auth" value="my_password_from_nxpassgen" />
> 
> instead of key="Password".
> 
> Sorry for that.
> 
> So now it gets somehow farther, but stops at "Negotiating protocol 
> version" in the browser. The log looks like that:
> 
> 
> 
> 
> stream created
> /home/tch/.mozilla/firefox/pyfsycb5.default/Cache/18EC3F91d01
> Info: /home/tch/.mozilla/firefox/pyfsycb5.default/Cache/18EC3F91d01.
> Info: moznx - version .2 (based on NXRUN - version 1.3.1-1).
> Info: NXConnection created.
> Info: setting 'NX_PersonalDirectory' to '/home/tch/.nx'.
> Info: checking cookie...
> Info: setting 'NX_CookieTempFilePath' to 
> '/home/tch/.nx/temp/8547/authlog'.Info: cookie found...
> Info: setting 'NX_SshPath' to '/usr/NX/bin/nxssh'.
> Info: setting 'NX_SshKeyPath' to '/usr/NX/share/client.id_dsa.key'.
> Info: setting 'NX_SshLogPath' to '/home/tch/.nx/temp/8547/sshlog'.
> SettingsToParameters : setting 'NX_SessionName' to 
> ''/home/tch/.mozilla/firefox/pyfsycb5.default/Cache/18EC3F91d01'.
> SettingsToParameters : setting 'NX_Username' to ' + tch'.
> SettingsToParameters : setting 'NX_PasswordMD5' to 'xxxxx'.
> SettingsToParameters : setting 'NX_HostName' to ''127.0.0.1'.
> SettingsToParameters : setting 'NX_HostPort' to 
> '%d'.SettingsToParameters : setting 'NX_LinkSpeed' to ''modem'.
> Info: setting 'NX_DesktopGeometry' to '800x600+0+0'.
> SettingsToParameters : setting 'NX_SessionType' to 'unix-rfb'.
> SettingsToParameters : setting 'NX_Keyboard' to 
> '%s'.SettingsToParameters : setting 'NX_EnableTcpNoDelay' to '1'.
> SettingsToParameters : setting 'NX_EnableStreamCompression' to 
> '%d'.1'.SettingsToParameters : setting 'NX_EnableEncryption' to '0'.
> SettingsToParameters : setting 'NX_RestoreCache' to '1'.
> SettingsToParameters : setting 'NX_CacheSizeInMemory' to ''8m'.
> SettingsToParameters : setting 'NX_CacheSizeOnDisk' to ''32m'.
> NXTransport (nxssh): creating new process.
> NXTransport (nxssh): new process created.
> NXTransport (nxssh): set flags for redirection.
> NXTransport (nxssh): set default parameter 'NX_SshName'.
> NXProcess: process being spawned /usr/NX/bin/nxssh
> NXTransport (nxssh): connecting...
> Info: Connecting to '127.0.0.1'.
> 
> ---
> READ: nxssh -nx -i /usr/NX/share/client.id_dsa.key nx at 127.0.0.1
> 
> ---
> NXProtocol: line does not contain token NX.
> NXProtocol: line is: nxssh -nx -i /usr/NX/share/client.id_dsa.key 
> nx at 127.0.0.1
> 
> ---
> READ: NX> 203 NXSSH running with pid: 8585
> 
> ---
> NXProtocol: parsed line has code '203' and string 'NXSSH running 
> with 
> pid: 8585 '.
> 
> ---
> READ: NX> 200 Connected to address: 127.0.0.1 on port: 22
> 
> ---
> NXProtocol: parsed line has code '200' and string 'Connected to 
> address: 
> 127.0.0.1 on port: 22 '.
> NXProtocol: connecting...
> 
> ---
> READ: NX> 202 Authenticating user: nx
> 
> ---
> NXProtocol: parsed line has code '202' and string 'Authenticating 
> user: 
> nx '.
> NXProtocol: connected.
> Info: Connected to '127.0.0.1'.
> 
> ---
> READ: NX> 208 Using auth method: publickey
> 
> ---
> NXProtocol: parsed line has code '208' and string 'Using auth 
> method: 
> publickey'.
> NXProtocol: skip NX code '208'
> 
> ---
> READ: HELLO NXSERVER - Version 1.4.0-02 OS_(GPL)
> NX> 105
> ---
> NXProtocol: set server version to '1.4.0'.
> NXProtocol: sending version.
> NXProtocol: parsed line has code '105' and string ''.
> NXProtocol: standard 'Hello' created
> NXProtocol: sending Hello... WRITE: Hello NXCLIENT - Version 1.4.0
> 
> success!
> NXProtocol: Hello NXCLIENT - Version 1.4.0
> Info: Negotiating protocol version.
> 
> ---
> READ: Hello NXCLIENT - Version 1.4.0
> NX> 105
> ---
> NXProtocol: line does not contain token NX.
> NXProtocol: line is: Hello NXCLIENT - Version 1.4.0
> NXProtocol: parsed line has code '105' and string ''.
> 
> 
> 
> Any clue?
> 
> Tomek
> _______________________________________________
> FreeNX-kNX mailing list
> FreeNX-kNX at kde.org
> https://mail.kde.org/mailman/listinfo/freenx-knx
>