OESF Portables Forum

Model Specific Forums => Sharp Zaurus => Zaurus - pdaXrom => Topic started by: ThirtyOne on June 27, 2005, 07:33:27 am

Title: Nxrun
Post by: ThirtyOne on June 27, 2005, 07:33:27 am: I maintain the nxrun client for NX. When paired with an NX server or FreeNX server, it allows you to create low-bandwidth x-based connections to a linux server.

Generally speaking, a connection uses about 20k and is more responsive than a remote X session and certainly faster than VNC.

NXRun is a command line client and very small and portable. It does require the open source nx libraries.

more info here: http://home.nc.rr.com/moznx/ (http://home.nc.rr.com/moznx/)

I wish I had time to set up a pdaXrom development environment and get this ported but I don't.

If anyone is willing to help with the port I can provide all the details.

Thanks,

Lawrence
Title: Nxrun
Post by: scoutme on June 27, 2005, 07:51:17 pm: I was thinking about nx for a while... let me know: I'd like to set it up and r.ing on pdaXrom
Title: Nxrun
Post by: adf on June 27, 2005, 11:35:17 pm: I'm not even sure about the rc 10 sdk? the rc 5 one works?
When I know that I'll happily give it a shot
Title: Nxrun
Post by: pgas on July 03, 2005, 01:16:45 pm: the sdk for rc9 works for rc10 http://www.pdaxrom.org/index.php?showid=40&menuid=11 (http://www.pdaxrom.org/index.php?showid=40&menuid=11)
(unless you need something that is only present in the latest libraries)

you can use the native sdk here http://212.10.30.205/rc10/Zaurus-7x0-860/ (http://212.10.30.205/rc10/Zaurus-7x0-860/)
for rc10 on you 6000 without a problem.
(mount -o loop zgcc-3.3.6.img /opt/native/arm/3.3.6-xscale-softvfp ,be sure to create the directory before)
Title: Nxrun
Post by: adf on July 04, 2005, 05:06:02 pm: Quote
the sdk for rc9 works for rc10 http://www.pdaxrom.org/index.php?showid=40&menuid=11 (http://www.pdaxrom.org/index.php?showid=40&menuid=11)
(unless you need something that is only present in the latest libraries)

you can use the native sdk here http://212.10.30.205/rc10/Zaurus-7x0-860/ (http://212.10.30.205/rc10/Zaurus-7x0-860/)
for rc10 on you 6000 without a problem.
(mount -o loop zgcc-3.3.6.img /opt/native/arm/3.3.6-xscale-softvfp ,be sure to create the directory before)
[div align=\"right\"][a href=\"index.php?act=findpost&pid=86847\"][{POST_SNAPBACK}][/a][/div]
Thanks! now I can do stuff
Title: Nxrun
Post by: ThirtyOne on August 22, 2005, 09:04:47 am: Now with a gui!

I have posted nxrun-gui.py on the freenx website. It is a gui that mimics the main features of the NXClient gui.

I know it runs on pdaxrom because I wrote it on my zaurus.

This is a *bump*. I am still looking for someone who has experience compiling for pdaxrom to compile the client.
Title: Nxrun
Post by: scoutme on August 22, 2005, 12:51:12 pm: up: it's very important
Title: Nxrun
Post by: jh on August 22, 2005, 02:27:46 pm: Quote
Now with a gui!

I have posted nxrun-gui.py on the freenx website. It is a gui that mimics the main features of the NXClient gui.

I know it runs on pdaxrom because I wrote it on my zaurus.

This is a *bump*. I am still looking for someone who has experience compiling for pdaxrom to compile the client.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=92834\"][{POST_SNAPBACK}][/a][/div]

I can give it a try sometime this week while watching some baseball

I've got the pdaxrom sdk setup, used it to compile a few things so far... this might be a bit more complicated than the stuff I've done, but it doesn't hurt to try.

Any pointers to what I need to start with?

jason
Title: Nxrun
Post by: ThirtyOne on August 22, 2005, 04:42:49 pm: Hey, Jason. Good to here from you. I hope the girls are doing well.

The main info on compiling the core nx client libraries are here:

http://web01.nomachine.com/documentation/b...-components.php (http://web01.nomachine.com/documentation/building-components.php)

We need:

nxssh
nxcomp
nxproxy

Then, you need the nxc libraries:

nxcompsh
nxdriver
nxrun

These files are in CVS on the freenx site. The gui can also be downloaded there.

freenx.berlios.de

The nxc components and the NX libraries are not linked together so they can be built separately.

- L
Title: Nxrun
Post by: jh on August 22, 2005, 06:51:33 pm: Howdy! Girls are doing great, thanks!

Ok... nxcomp and nxproxy compiled pretty easily. nxssh is being kind of a pain since it wants to compile all sorts of test programs in the configure script even though I'm cross-compiling. I've edited by hand (hacked) the configure script for a few of them but there are a lot more to go. I'll either find a better way or finish those hacks tonight.

Where are those other components in svn?

jason
Title: Nxrun
Post by: ThirtyOne on August 22, 2005, 07:43:17 pm: Sounds like some good progress!

They have switched the server over to svn, but all my client stuff is still in cvs.

There is another python client in svn but it is incomplete and does not use the nxdriver library that implements most of the protocol. I have never looked at it but it may be interesting.
Title: Nxrun
Post by: pgas on October 04, 2005, 02:21:02 pm: I've compiled the module, but I didn't tested it ..(don't know much about NX)
the binaries are in /usr/NX/bin.

I've attached a sample session file given to me by the folks on #nx.

If someone wants to try ...
Title: Nxrun
Post by: DaMightyWhightyMan on October 06, 2005, 04:46:13 pm: Quote
I've compiled the module, but I didn't tested it ..(don't know much about NX)
the binaries are in /usr/NX/bin.

I've attached a sample session file given to me by the folks on #nx.

If someone wants to try ...
[div align=\"right\"][a href=\"index.php?act=findpost&pid=98160\"][{POST_SNAPBACK}][/a][/div]

cool, thanks gang
Title: Nxrun
Post by: ThirtyOne on October 13, 2005, 07:23:23 am: Thanks to pgas!

I have used these binaries to successfully connect to some nx servers!

I definitely need to write a how-to because there were some tweaks I had to make to get it going.

I will post the steps here soon.

Also, I had trouble connecting to a 1.5.0 nomachine server, but it worked fine against a couple of 1.4.x FreeNX servers. I will try and track the issue down.

Thanks again for your help!
Title: Nxrun
Post by: adf on October 14, 2005, 02:28:32 am: Quote
Thanks to pgas!

I have used these binaries to successfully connect to some nx servers!

I definitely need to write a how-to because there were some tweaks I had to make to get it going.

I will post the steps here soon.

Also, I had trouble connecting to a 1.5.0 nomachine server, but it worked fine against a couple of 1.4.x FreeNX servers. I will try and track the issue down.

Thanks again for your help!
[div align=\"right\"][a href=\"index.php?act=findpost&pid=99162\"][{POST_SNAPBACK}][/a][/div]

That'd be handy- I look forward to it!
Title: Nxrun
Post by: ThirtyOne on October 14, 2005, 02:05:13 pm: Ok - Here is a quick how-to that I hope will allow someone other than me to use nx.

1. Getting the gui working
a. You need a few python files in addition to nxrun-gui.py. I am attaching them here: subprocess.py and pickle.py. NOTE: I had to change the extensions to upload them so you need to change them from .txt to .py. All of these files should be placed in /usr/NX/bin
b. You need to create the config directory. mkdir /usr/NX/bin/config/

2. You need to export a HOSTNAME variable or else it fails. I will change this code to use a default in the future. For now, you need to export HOSTNAME="zaurus" or something similar

3. You need to have the client authentication key. I have attached the standard nomachine client key. NOTE: I had to change the extension to upload it so you need to change it from .txt to .key. It needs to be placed in /usr/NX/share/client.id_dsa.key

4. You should ssh into your server at least once before attempting to connect. There is code that is supposed to intercept the warning when you connect to a new server and agree to add the key. This is not working consistently so it is better to check yourself.

5. Once you have this done you can start the gui ./nxrun-gui.py. If you are familiar with the nomachine client you should know how it works. There is a tutorial on linuxjournal.com right now that may help. Just type the name of a config into the Service entry field and hit Configure... When you are prompted, select the Create button and create a new configuration.

6. If you are having trouble, use nxrun directly and post the log file. You can type nxrun config/<your session name>.conf -i -fide. This will create nxcompsh.log with all the details.
Title: Nxrun
Post by: DaMightyWhightyMan on October 14, 2005, 04:38:37 pm: Quote
Thanks to pgas!

I have used these binaries to successfully connect to some nx servers!

I definitely need to write a how-to because there were some tweaks I had to make to get it going.

I will post the steps here soon.

Also, I had trouble connecting to a 1.5.0 nomachine server, but it worked fine against a couple of 1.4.x FreeNX servers. I will try and track the issue down.

Thanks again for your help!
[div align=\"right\"][a href=\"index.php?act=findpost&pid=99162\"][{POST_SNAPBACK}][/a][/div]

that how-to would be nice, i couldn't get it to work
Title: Nxrun
Post by: ThirtyOne on October 14, 2005, 05:09:46 pm: Did you see my notes above? How far did you get?
Title: Nxrun
Post by: DaMightyWhightyMan on October 19, 2005, 05:36:32 pm: Quote
Did you see my notes above? How far did you get?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=99417\"][{POST_SNAPBACK}][/a][/div]

Im a retard and didn't see there was a 2nd page, I'll try out your steps when i get a chance. thanks for the howto!
Title: Nxrun
Post by: aaaweez on February 09, 2006, 03:48:43 am: I have created a config directory as specified in the directions above:
b. You need to create the config directory. mkdir /usr/NX/bin/config/

Code: [Select]
# ls -lh /usr/NX/bin/ drwxr-xr-x 2 root root 0 Feb 9 07:20 config lrwxrwxrwx 1 root root 28 Feb 9 07:17 nxproxy -> /mnt/card/usr/NX/bin/nxproxy lrwxrwxrwx 1 root root 26 Feb 9 07:17 nxrun -> /mnt/card/usr/NX/bin/nxrun -rwxr-xr-x 1 root root 64.5k Feb 9 07:19 nxrun_gui.py lrwxrwxrwx 1 root root 26 Feb 9 07:18 nxssh -> /mnt/card/usr/NX/bin/nxssh -rwxr-xr-x 1 root root 43.8k Feb 9 07:19 pickle.py -rw-r--r-- 1 root root 36.6k Feb 9 07:22 pickle.pyc -rwxr-xr-x 1 root root 41.4k Feb 9 07:20 subprocess.py -rw-r--r-- 1 root root 29.3k Feb 9 07:22 subprocess.pyc
but this is what I am seeing..

Code: [Select]
# ./nxrun_gui.py Traceback (most recent call last): File "./nxrun_gui.py", line 692, in config_dlg_do_response self.save_options() File "./nxrun_gui.py", line 1606, in save_options FD = open("./config/" + service, "w") IOError: [Errno 21] Is a directory: './config/' Traceback (most recent call last): File "./nxrun_gui.py", line 688, in config_dlg_do_response self.save_options() File "./nxrun_gui.py", line 1606, in save_options FD = open("./config/" + service, "w") IOError: [Errno 21] Is a directory: './config/'
I look at the code a bit, but python is not my main thing, and I seriously need to go to bed soon, so I thought I would post some feedback.

BTW thanks for the instructions and thanks pgas for the compiling work . I cant wait to get this working, as i use nomachine for everything.

-aaaweez
Title: Nxrun
Post by: ThirtyOne on February 09, 2006, 12:19:44 pm: I have to admit I haven't been working on the gui in a while.

I think your problem is you have to type a name into the session combobox before you hit the configure button. It looks like it is trying to save the configuration file but there is no config filename.

Let me know if that addresses the problem.
Title: Nxrun
Post by: aaaweez on February 09, 2006, 03:17:14 pm: cool, that sounds pretty reasonable. I will check that out later today/tonight. Thanks so much for the reply.

-aaaweez
Title: Nxrun
Post by: aaaweez on February 10, 2006, 01:45:38 am: You were dead on about need for a name. That fixed it up promptly.

Unfortunately, I am running a 1.5 server here on my desktop, so it might not eve
n be possible to connect. Here is what I am getting when I run the following:
./nxrun config/hoopyfoo.conf -i -l ide

I am only including the last bit of the output, as I imagine the rest is not nee
ded, and this is a buttload of output. I apologize in advance if ths is too muc
h output to post. Should I be using a link to the content elsewhere?
Code: [Select]
--- DEBUG: NXProtocol: line does not contain token NX. DEBUG: NXProtocol: line is: ******* DEBUG: --- READ: NX> 103 Welcome to: hoopy user: aaaweez NX> 105 --- DEBUG: NXProtocol: parsed line has code '103' and string 'Welcome to: hoopy user : aaaweez'. INFO: NXProtocol: authenticated. DEBUG: NXProtocol: parsed line has code '105' and string ''. DEBUG: NXProtocol: starting session... DEBUG: WRITE: startsession DEBUG: NXProtocol: creating options for server connection. DEBUG: NXProtocol: set option 'session' to 'config/hoopyfoo'. DEBUG: NXProtocol: set option 'cookie' to 'd83a23653651b4855474ca19374a4776'. DEBUG: NXProtocol: set option 'type' to 'unix-kde'. DEBUG: NXProtocol: set option 'cache' to '4m'. DEBUG: NXProtocol: set option 'link' to 'LAN'. DEBUG: NXProtocol: set option 'geometry' to '800x600+0+0'. DEBUG: NXProtocol: set option 'keyboard' to 'us'. DEBUG: NXProtocol: set option 'encryption' to '0'. DEBUG: NXProtocol: set option 'cache' to '1'. DEBUG: NXProtocol: set option 'nodelay' to '1'. DEBUG: NXProtocol: set option 'stream' to '1'. DEBUG: NXProtocol: set option 'media' to '0'. DEBUG: NXProtocol: set option 'samba' to '0'. DEBUG: NXProtocol: set option 'images' to '16m'. DEBUG: NXProtocol: options for server = '--session="config/hoopyfoo" --cookie="d 83a23653651b4855474ca19374a4776" --type="unix-kde" --cache="4m" --link="LAN" --g eometry="800x600+0+0" --keyboard="us" --encryption="0" --cache="1" --nodelay="1" --stream="1" --media="0" --samba="0" --images="16m"'. DEBUG: NXProtocol: sending parameters... DEBUG: WRITE: --session="config/hoopyfoo" --cookie="d83a23653651b4855474ca19374a 4776" --type="unix-kde" --cache="4m" --link="LAN" --geometry="800x600+0+0" --key board="us" --encryption="0" --cache="1" --nodelay="1" --stream="1" --media="0" - -samba="0" --images="16m" DEBUG: NXProtocol: parameters sent '--session="config/hoopyfoo" --cookie="d83a23 653651b4855474ca19374a4776" --type="unix-kde" --cache="4m" --link="LAN" --geomet ry="800x600+0+0" --keyboard="us" --encryption="0" --cache="1" --nodelay="1" --st ream="1" --media="0" --samba="0" --images="16m"'. INFO: Negotiating session parameters. I> Negotiating session parameters. DEBUG: --- READ: Start session with: --session="config\057hoopyfoo" --cookie="************* *******************" --type="unix-kde" --cache="4m" --link="LAN" --geometry="800 x600+0+0" --keyboard="us" --encryption="0" --cache="1" --nodelay="1" --stream="1 " --media="0" --samba="0" --images="16m" --- DEBUG: NXProtocol: line does not contain token NX. DEBUG: NXProtocol: line is: Start session with: --session="config\057hoopyfoo" - -cookie="********************************" --type="unix-kde" --cache="4m" --link ="LAN" --geometry="800x600+0+0" --keyboard="us" --encryption="0" --cache="1" --n odelay="1" --stream="1" --media="0" --samba="0" --images="16m" DEBUG: --- READ: NX> 700 Session id: hoopy-1002-7C43DE0B0CE8565A4EE6E056EA3F0662 NX> 705 Session display: 1002 NX> 703 Session type: unix-kde NX> 701 Proxy cookie: E755826A242CAF2854DA9700B04770F0 NX> 702 Proxy IP: 192.168.xx.36 NX> 706 Agent cookie: d83a23653651b4855474ca19374a4776 NX> 704 Session cache: unix-kde NX> 707 SSL tunneling: 0 NX> 710 Session status: running NX> 105 --- DEBUG: NXProtocol: parsed line has code '700' and string 'Session id: hoopy-1002 -7C43DE0B0CE8565A4EE6E056EA3F0662'. DEBUG: NXProtocol: skip NX code '700' DEBUG: NXProtocol: parsed line has code '705' and string 'Session display: 1002' . DEBUG: NXProtocol: skip NX code '705' DEBUG: NXProtocol: parsed line has code '703' and string 'Session type: unix-kde '. DEBUG: NXProtocol: skip NX code '703' DEBUG: NXProtocol: parsed line has code '701' and string 'Proxy cookie: E755826A 242CAF2854DA9700B04770F0'. DEBUG: NXProtocol: skip NX code '701' DEBUG: NXProtocol: parsed line has code '702' and string 'Proxy IP: 192.168.xx36 '. DEBUG: NXProtocol: skip NX code '702' DEBUG: NXProtocol: parsed line has code '706' and string 'Agent cookie: d83a2365 3651b4855474ca19374a4776'. DEBUG: NXProtocol: skip NX code '706' DEBUG: NXProtocol: parsed line has code '704' and string 'Session cache: unix-kd e'. DEBUG: NXProtocol: skip NX code '704' DEBUG: NXProtocol: parsed line has code '707' and string 'SSL tunneling: 0'. DEBUG: NXProtocol: skip NX code '707' DEBUG: NXProtocol: parsed line has code '710' and string 'Session status: runnin g'. INFO: NXProtocol: session accepted (proxy needed). DEBUG: NXProtocol: parsed line has code '105' and string ''. DEBUG: NXProtocol: setting parameters negotiated with server. DEBUG: NXProtocol: line does not contain token NX. DEBUG: NXProtocol: line is: DEBUG: nxssh DEBUG: NXProtocol: line does not contain token NX. DEBUG: NXProtocol: line is: DEBUG: -nx DEBUG: NXProtocol: line does not contain token NX. DEBUG: NXProtocol: line is: DEBUG: -i DEBUG: NXProtocol: line does not contain token NX. DEBUG: NXProtocol: line is: DEBUG: /usr/NX/share/client.id_dsa.key DEBUG: NXProtocol: line does not contain token NX. DEBUG: NXProtocol: line is: DEBUG: nx@192.168.xx.31 DEBUG: NXProtocol: line does not contain token NX. DEBUG: NXProtocol: line is: DEBUG: -p DEBUG: NXProtocol: line does not contain token NX. DEBUG: NXProtocol: line is: DEBUG: 22 DEBUG: NXProtocol: line does not contain token NX. DEBUG: NXProtocol: line is: DEBUG: - end process args DEBUG: NXProtocol: parsed line has code '203' and string 'NXSSH running with pid : 15285'. DEBUG: NXProtocol: setting parameter from server DEBUG: NXProtocol: parsed line has code '200' and string 'Connected to address: 192.168.xx.31 on port: 22'. DEBUG: NXProtocol: setting parameter from server DEBUG: NXProtocol: parsed line has code '202' and string 'Authenticating user: n x'. DEBUG: NXProtocol: setting parameter from server DEBUG: NXProtocol: parsed line has code '208' and string 'Using auth method: pub lickey'. DEBUG: NXProtocol: setting parameter from server DEBUG: NXProtocol: setting parameter from server DEBUG: NXProtocol: parsed line has code '105' and string 'Hello NXCLIENT - Versi on 1.4.0'. DEBUG: NXProtocol: setting parameter from server DEBUG: NXProtocol: parsed line has code '134' and string 'Accepted protocol: 1.4 .0'. DEBUG: NXProtocol: setting parameter from server DEBUG: NXProtocol: parsed line has code '105' and string 'Set shell_mode: shell' . DEBUG: NXProtocol: setting parameter from server DEBUG: NXProtocol: parsed line has code '105' and string 'Login '. DEBUG: NXProtocol: setting parameter from server DEBUG: NXProtocol: parsed line has code '101' and string 'User: aaaweez'. DEBUG: NXProtocol: setting parameter from server DEBUG: NXProtocol: parsed line has code '102' and string 'Password: *******'. DEBUG: NXProtocol: setting parameter from server DEBUG: NXProtocol: parsed line has code '103' and string 'Welcome to: hoopy user : aaaweez'. DEBUG: NXProtocol: setting parameter from server DEBUG: NXProtocol: parsed line has code '105' and string 'Start session with: -- session="config\057hoopyfoo" --cookie="********************************" --type= "unix-kde" --cache="4m" --link="LAN" --geometry="800x600+0+0" --keyboard="us" -- encryption="0" --cache="1" --nodelay="1" --stream="1" --media="0" --samba="0" -- images="16m" '. DEBUG: NXProtocol: setting parameter from server DEBUG: NXProtocol: parsed line has code '700' and string 'Session id: hoopy-1002 -7C43DE0B0CE8565A4EE6E056EA3F0662'. DEBUG: NXProtocol: setting parameter from server DEBUG: NXProtocol: set parameter = hoopy-1002-7C43DE0B0CE8565A4EE6E056EA3F0662 DEBUG: NXProtocol: set ID = hoopy-1002-7C43DE0B0CE8565A4EE6E056EA3F0662 DEBUG: NXProtocol: parsed line has code '705' and string 'Session display: 1002' . DEBUG: NXProtocol: setting parameter from server DEBUG: NXProtocol: set parameter = 1002 DEBUG: NXProtocol: set Port = 1002. DEBUG: NXProtocol: parsed line has code '703' and string 'Session type: unix-kde '. DEBUG: NXProtocol: setting parameter from server DEBUG: NXProtocol: set parameter = unix-kde DEBUG: NXProtocol: set Session Type = unix-kde. DEBUG: NXProtocol: parsed line has code '701' and string 'Proxy cookie: E755826A 242CAF2854DA9700B04770F0'. DEBUG: NXProtocol: setting parameter from server DEBUG: NXProtocol: set parameter = E755826A242CAF2854DA9700B04770F0 DEBUG: NXProtocol: set Cookie = E755826A242CAF2854DA9700B04770F0. DEBUG: NXProtocol: parsed line has code '702' and string 'Proxy IP: 192.168.xx.3 6'. DEBUG: NXProtocol: setting parameter from server DEBUG: NXProtocol: set parameter = 192.168.xx.36 DEBUG: NXProtocol: set Server = 192.168.xx.36. DEBUG: NXProtocol: parsed line has code '706' and string 'Agent cookie: d83a2365 3651b4855474ca19374a4776'. DEBUG: NXProtocol: setting parameter from server DEBUG: NXProtocol: set parameter = d83a23653651b4855474ca19374a4776 DEBUG: NXProtocol: set Agent Cookie = d83a23653651b4855474ca19374a4776. DEBUG: NXProtocol: parsed line has code '704' and string 'Session cache: unix-kd e'. DEBUG: NXProtocol: setting parameter from server DEBUG: NXProtocol: set parameter = unix-kde DEBUG: NXProtocol: parsed line has code '707' and string 'SSL tunneling: 0'. DEBUG: NXProtocol: setting parameter from server DEBUG: NXProtocol: set parameter = 0 DEBUG: NXProtocol: set SSL Tunneling = 0. DEBUG: NXProtocol: parsed line has code '710' and string 'Session status: runnin g'. DEBUG: NXProtocol: setting parameter from server DEBUG: NXProtocol: set parameter = running DEBUG: NXProtocol: parsed line has code '105' and string ''. DEBUG: NXProtocol: setting parameter from server DEBUG: NXProtocol: parameters stored. DEBUG: NXProtocol: Sending Bye... DEBUG: WRITE: bye DEBUG: NXProtocol: closing connection... DEBUG: WRITE: exit INFO: Starting session. I> Starting session. S> hoopy-1002-7C43DE0B0CE8565A4EE6E056EA3F0662 DEBUG: create proxy connection. DEBUG: NXProxy: initializing... DEBUG: NXProxy: creating new process. DEBUG: NXProxy: new process created. DEBUG: NXProxy: set flags for redirection. DEBUG: NXProxy: set default parameter 'NX_ProxyName'. DEBUG: NXProcess: argument '-S' added. DEBUG: NXProxy: parameter 'NX_ProxyLogPath' is empty. DEBUG: NXProtocol: parameter 'NX_ProxySessionId' is empty. DEBUG: NXProxy: set default parameter 'NX_ProxyLogPath'. DEBUG: NXProxy: initializing options. DEBUG: NXProxy: parameter 'NX_ProxyRoot' is empty. DEBUG: NXProxy: set default parameter 'NX_ProxyRoot'. DEBUG: NXProtocol: creating options for proxy connection. DEBUG: NXProtocol: set option 'session' to 'config/hoopyfoo'. DEBUG: NXProtocol: set option 'cookie' to 'E755826A242CAF2854DA9700B04770F0'. DEBUG: NXProtocol: set option 'root' to '/home/root/.nx'. DEBUG: NXProtocol: set option 'id' to 'hoopy-1002-7C43DE0B0CE8565A4EE6E056EA3F06 62'. DEBUG: NXProtocol: set option 'connect' to '192.168.xx.31:1002'. DEBUG: NXProtocol: options for proxy = 'nx,session=config/hoopyfoo,cookie=E75582 6A242CAF2854DA9700B04770F0,root=/home/root/.nx,id=hoopy-1002-7C43DE0B0CE8565A4EE 6E056EA3F0662,connect=192.168.xx.31:1002'. DEBUG: NXProxy: parameter 'NX_ProxyOptionsPath' is empty. DEBUG: NXProxy: set default parameter 'NX_ProxyOptionsPath'. DEBUG: NXProcess: argument 'options=/home/root/.nx/S-hoopy-1002-7C43DE0B0CE8565A 4EE6E056EA3F0662/options:1002' added. DEBUG: NXProxy: buffer cleared. DEBUG: NXProxy: starting... DEBUG: NXProxy: using library path '/usr/NX/lib'. DEBUG: NXProxy: using library path '/usr/NX/lib:/usr/lib/kde/lib:/opt/native/arm /3.4.5-xscale-softvfp/lib'. DEBUG: new library path: /usr/NX/lib:/usr/lib/kde/lib:/opt/native/arm/3.4.5-xsca le-softvfp/lib DEBUG: NXProcess: process being spawned /usr/NX/bin/nxproxy DEBUG: NXProxy: connecting... DEBUG: --- READ: Bye NX> 999 Bye --- DEBUG: NXProtocol: line does not contain token NX. DEBUG: NXProtocol: line is: Bye DEBUG: NXProtocol: parsed line has code '999' and string 'Bye'. INFO: NXProtocol: connection closed. DEBUG: NXProtocol: searching for error... DEBUG: NXProtocol: line does not contain token NX. DEBUG: NXProtocol: line is: DEBUG: nxssh DEBUG: NXProtocol: line does not contain token NX. DEBUG: NXProtocol: line is: DEBUG: -nx DEBUG: NXProtocol: line does not contain token NX. DEBUG: NXProtocol: line is: DEBUG: -i DEBUG: NXProtocol: line does not contain token NX. DEBUG: NXProtocol: line is: DEBUG: /usr/NX/share/client.id_dsa.key DEBUG: NXProtocol: line does not contain token NX. DEBUG: NXProtocol: line is: DEBUG: nx@192.168.xx.31 DEBUG: NXProtocol: line does not contain token NX. DEBUG: NXProtocol: line is: DEBUG: -p DEBUG: NXProtocol: line does not contain token NX. DEBUG: NXProtocol: line is: DEBUG: 22 DEBUG: NXProtocol: line does not contain token NX. DEBUG: NXProtocol: line is: DEBUG: - end process args DEBUG: NXProtocol: parsed line has code '203' and string 'NXSSH running with pid : 15285'. DEBUG: NXProtocol: parsed line has code '200' and string 'Connected to address: 192.168.xx.31 on port: 22'. DEBUG: NXProtocol: parsed line has code '202' and string 'Authenticating user: n x'. DEBUG: NXProtocol: parsed line has code '208' and string 'Using auth method: pub lickey'. DEBUG: NXProtocol: parsed line has code '105' and string 'Hello NXCLIENT - Versi on 1.4.0'. DEBUG: NXProtocol: parsed line has code '134' and string 'Accepted protocol: 1.4 .0'. DEBUG: NXProtocol: parsed line has code '105' and string 'Set shell_mode: shell' . DEBUG: NXProtocol: parsed line has code '105' and string 'Login '. DEBUG: NXProtocol: parsed line has code '101' and string 'User: aaaweez'. DEBUG: NXProtocol: parsed line has code '102' and string 'Password: *******'. DEBUG: NXProtocol: parsed line has code '103' and string 'Welcome to: hoopy user : aaaweez'. DEBUG: NXProtocol: parsed line has code '105' and string 'Start session with: -- session="config\057hoopyfoo" --cookie="********************************" --type= "unix-kde" --cache="4m" --link="LAN" --geometry="800x600+0+0" --keyboard="us" -- encryption="0" --cache="1" --nodelay="1" --stream="1" --media="0" --samba="0" -- images="16m" '. DEBUG: NXProtocol: parsed line has code '700' and string 'Session id: hoopy-1002 -7C43DE0B0CE8565A4EE6E056EA3F0662'. DEBUG: NXProtocol: parsed line has code '705' and string 'Session display: 1002' . DEBUG: NXProtocol: parsed line has code '703' and string 'Session type: unix-kde '. DEBUG: NXProtocol: parsed line has code '701' and string 'Proxy cookie: E755826A 242CAF2854DA9700B04770F0'. DEBUG: NXProtocol: parsed line has code '702' and string 'Proxy IP: 192.168.xx.3 6'. DEBUG: NXProtocol: parsed line has code '706' and string 'Agent cookie: d83a2365 3651b4855474ca19374a4776'. DEBUG: NXProtocol: parsed line has code '704' and string 'Session cache: unix-kd e'. DEBUG: NXProtocol: parsed line has code '707' and string 'SSL tunneling: 0'. DEBUG: NXProtocol: parsed line has code '710' and string 'Session status: runnin g'. DEBUG: NXProtocol: parsed line has code '105' and string 'Bye '. DEBUG: NXProtocol: parsed line has code '999' and string 'Bye'. DEBUG: NXProtocol: error not found. DEBUG: --- READ: DEBUG: nxproxy DEBUG: -S DEBUG: options=/home/root/.nx/S-hoopy-1002-7C43DE0B0CE8565A4EE6E056EA3F0662/opti ons:1002 DEBUG: - end process args --- DEBUG: NXProtocol: DEBUG: nxproxy DEBUG: NXProtocol: DEBUG: -S DEBUG: NXProtocol: DEBUG: options=/home/root/.nx/S-hoopy-1002-7C43DE0B0CE8565A4E E6E056EA3F0662/options:1002 DEBUG: NXProtocol: DEBUG: - end process args INFO: Negotiating link parameters. DEBUG: --- READ: NX> 596 Error: Session restore failed: Couldn't open the display. --- DEBUG: NXProtocol: parsed line has code '596' and string 'Error: Session restore failed: Couldn't open the display.'. DEBUG: NXProtocol: skip NX code '596' ERROR: NXProtocol: error found. ERROR: NXProtocol: error code 596 = Error: Session restore failed: Couldn't open the display.. DEBUG: NXTransport (nxssh): break connection. Error: Session restore failed: Couldn't open the display. ERROR: Error: Session restore failed: Couldn't open the display. E> Error: Session restore failed: Couldn't open the display. INFO: Error occurred. For more info check '/home/root/.nx/temp/15278/sshlog'. I> Error occurred. For more info check '/home/root/.nx/temp/15278/sshlog'. DEBUG: NXConnection's destructor called. DEBUG: cleaning up NXConnection. DEBUG: deleting Server Connection DEBUG: NXConnection clean.

contents of /home/root/.nx/temp/15278/sshlog is a more succinct version of above
.
Code: [Select]
DEBUG: nxssh DEBUG: -nx DEBUG: -i DEBUG: /usr/NX/share/client.id_dsa.key DEBUG: nx@192.168.xx.31 DEBUG: -p DEBUG: 22 DEBUG: - end process args NX> 203 NXSSH running with pid: 15285 NX> 200 Connected to address: 192.168.xx.31 on port: 22 NX> 202 Authenticating user: nx NX> 208 Using auth method: publickey HELLO NXSERVER - Version 1.5.0-91 NX> 105 Hello NXCLIENT - Version 1.4.0 NX> 134 Accepted protocol: 1.4.0 NX> 105 Set shell_mode: shell NX> 105 Login NX> 101 User: aaaweez NX> 102 Password: ******* NX> 103 Welcome to: hoopy user: aaaweez NX> 105 Start session with: --session="config\057hoopyfoo" --cookie="*********** *********************" --type="unix-kde" --cache="4m" --link="LAN" --geometry="8 00x600+0+0" --keyboard="us" --encryption="0" --cache ="1" --nodelay="1" --stream="1" --media="0" --samba="0" --images="16m" NX> 700 Session id: hoopy-1002-7C43DE0B0CE8565A4EE6E056EA3F0662 NX> 705 Session display: 1002 NX> 703 Session type: unix-kde NX> 701 Proxy cookie: E755826A242CAF2854DA9700B04770F0 NX> 702 Proxy IP: 192.168.xx.36 NX> 706 Agent cookie: d83a23653651b4855474ca19374a4776 NX> 704 Session cache: unix-kde NX> 707 SSL tunneling: 0 NX> 710 Session status: running NX> 105 Bye NX> 999 Bye NX> 596 Error: Session restore failed: Couldn't open the display. Killed by signal 15.
Server side showed this:
Code: [Select]
Feb 10 00:29:36 hoopy sshd[862]: Connection from 192.168.xx.36 port 1087 Feb 10 00:29:36 hoopy sshd[862]: Found matching DSA key: 4b:9b:38:6b:24:33:6b:48 :e4:f8:c4:5b:c9:f1:fd:98 Feb 10 00:29:36 hoopy sshd[862]: Accepted publickey for nx from 192.168.xx.36 po rt 1087 ssh2 Feb 10 00:29:36 hoopy sshd(pam_unix)[864]: session opened for user nx by (uid=0) Feb 10 00:29:37 hoopy sshd[871]: Connection from 127.0.0.1 port 60271 Feb 10 00:29:37 hoopy sshd[871]: Accepted keyboard-interactive/pam for aaaweez f rom 127.0.0.1 port 60271 ssh2 Feb 10 00:29:37 hoopy sshd(pam_unix)[874]: session opened for user aaaweez by (u id=0) Feb 10 00:29:37 hoopy sshd[874]: Connection closed by 127.0.0.1 Feb 10 00:29:37 hoopy sshd(pam_unix)[874]: session closed for user aaaweez Feb 10 00:29:37 hoopy 1.5.0-91[865]: User 'aaaweez' logged in from '192.168.xx.3 6'. 'NXLogin::set' Feb 10 00:29:37 hoopy sshd[874]: Closing connection to 127.0.0.1 Feb 10 00:29:37 hoopy 1.5.0-91[865]: Found a suspended session with id '7C43DE0B 0CE8565A4EE6E056EA3F0662' 'NXShell::Static' Feb 10 00:29:37 hoopy 1.5.0-91[865]: Suspended session is the same type 'unix-kd e' 'NXShell::Static' Feb 10 00:29:37 hoopy 1.5.0-91[865]: Suspended session has compatible geometry ' NXShell::Static' Feb 10 00:29:37 hoopy 1.5.0-91[865]: Restoring session with id: 7C43DE0B0CE8565A 4EE6E056EA3F0662 'NXShell::handler_session_start' Feb 10 00:29:37 hoopy sshd[876]: Connection from 127.0.0.1 port 60272 Feb 10 00:29:37 hoopy sshd[876]: Found matching DSA key: a8:b4:c5:0c:40:50:fd:c1 :de:20:f9:e5:21:c2:72:e7 Feb 10 00:29:37 hoopy sshd[876]: Found matching DSA key: a8:b4:c5:0c:40:50:fd:c1 :de:20:f9:e5:21:c2:72:e7 Feb 10 00:29:37 hoopy sshd[876]: Accepted publickey for aaaweez from 127.0.0.1 p ort 60272 ssh2 Feb 10 00:29:37 hoopy sshd(pam_unix)[878]: session opened for user aaaweez by (u id=0) Feb 10 00:29:38 hoopy 1.5.0-91[879]: INFO: Using port '1002' on node 'hoopy' for session 'unix-kde'. 'main:nxnode:6263' Feb 10 00:29:38 hoopy 1.5.0-91[865]: User 'aaaweez' from '192.168.xx.36' logged out. 'NXLogin::reset' Feb 10 00:29:40 hoopy 1.5.0-91[20584]: ERROR: Ignoring message status 'Terminati ng' on session id: 7C43DE0B0CE8565A4EE6E056EA3F0662 'NXShell::nxsessionSetStatus ' Feb 10 00:29:43 hoopy sshd[878]: Connection closed by 127.0.0.1 Feb 10 00:29:43 hoopy sshd(pam_unix)[878]: session closed for user aaaweez Feb 10 00:29:43 hoopy sshd[878]: Closing connection to 127.0.0.1 Feb 10 00:29:50 hoopy sshd[864]: Connection closed by 192.168.xx.36 Feb 10 00:29:50 hoopy sshd(pam_unix)[864]: session closed for user nx Feb 10 00:29:50 hoopy sshd[864]: Closing connection to 192.168.xx.36
thank you for any light you can shed on this.

-aaaweez
Title: Nxrun
Post by: ThirtyOne on February 10, 2006, 06:48:28 am: Hmmm. Well, there is a message about session restore. Perhaps try making sure you have no suspended sessions on your server for this user and clear up the cache files on the server and client before trying again.

I am not sure if it will work. I did get it to work with FreeNX a few times.

Ufortunately, lately I have been focusing my time more on fixing their browser plugin than on nxrun.
Title: Nxrun
Post by: diJenerate on July 26, 2006, 01:39:28 pm: Quote
...Ufortunately, lately I have been focusing my time more on fixing their browser plugin than on nxrun.
[div align=\"right\"][{POST_SNAPBACK}][/a][/div] (http://index.php?act=findpost&pid=114379\")

Hi, I'm wondering something... does that moznx plugin for linux work on any platform or is it arch dependent?

I'd like to use it from my Realm Systems [a href=\"http://projectblackdog.com/]Blackdog MPS[/url] so can I use the regular linux moznx plugin on this or must I compile nxrun for ppc?

Additionally, if it is platform dependent and I wanted to create a java based client, what should I be looking to change in the build method?

I really would love to see a nomachine client compiled for WinCE.net, Winmobile 2k5, Maemo and OE based distros with Opie (other than the ancient sl-5500 client), GPE and Ã…ngstrÃ¶m.

I have no problem using a MS based handheld if I can see a system with a real OS over NX in order to actually be productive.

diJenerate
Title: Nxrun
Post by: ThirtyOne on July 28, 2006, 10:55:27 am: Quote
Hi, I'm wondering something... does that moznx plugin for linux work on any platform or is it arch dependent?

The good thing about moznx is that it is completely open source - just like nxrun. If you can compile it you can run it. It already runs on Windows and Linux, so most other platforms are just variations. I already had a guy tell me he was porting to OS/2 with some success. It is a binary, however, so it has to be compiled to work.

Quote
Additionally, if it is platform dependent and I wanted to create a java based client, what should I be looking to change in the build method?

That being said, you have to be able to compile all the nomachine open source client components to get it to work, so I have never seen the point of a solution that was not binary. As long as you are compiling the nomachine components, why not compile the client as well. For what it is worth, there are java clients out there, but they still require the patform-dependent nomachine components to run, so the applets cannot run aribitrarily on any platform.

Moznx and nxrun share a library that implement the nomachine protocol. Unfortunately, the protocol is a pain. They are constantly changing it and nomachine and freeNX are not 100% compatible. The various versions of clients and servers are not fully compatible.

I have about given up on the nxc library and I am focusing on some other things but they unfortunately depend on the closed-source client.

Luckily there is another developer working on nxc with support from Google Summer of Code. However, he has not updated the published source code as far as I can see. I do expect him to and I hope he will improve its stability.

Also, a quick plug for my friends at cosmopod.com. If you don't understand how seriously cool NX is, then this site will give you a very easy way to check it out.
Title: Nxrun
Post by: loic on August 03, 2006, 11:21:36 am: Hello,
I work with freenx (0.4.4) and nxrun. It's good. I would like to work with moznx but it doesn't run.
The plugin moznx.xpi is installed on the client PC (it 's written in the log files) and the file NX conf is well located on the web server but mozilla bugs.
For the browser, I have used Mozilla Firefox 1.0.6, and Mozilla 1.7.11 too.
The client and the server work with Mandriva 2006.
(moznx version 0.3)

mozilla -p
INFO:
/home/loic/.mozilla/default/t0aaeca8.slt/Cache/A4269850d01.
INFO: moznx - version .3 (based on NXRUN - version 1.3.1-1).
DEBUG: NXConnection created.
DEBUG: setting 'NX_PersonalDirectory' to '/home/loic/.nx'.
DEBUG: checking cookie...
DEBUG: Info: setting 'NX_CookieTempFilePath' to
'/home/loic/.nx/temp/13124/authlog'.
DEBUG: NXCookie: display is '0'.
DEBUG: NXCookie: executing command 'xauth -f
/home/loic/.Xauthority list | grep MIT-MAGIC-COOKIE-1 | grep
"localhost/unix:0" | cut -f 5 -d ' '
1>/home/loic/.nx/temp/13124/authlog'.
DEBUG: NXCookie: command executed.
Erreur de segmentation

As you can see, mozilla "Error segmentation".
Do you know any solution to this problem please, or an other version of moznx to see if it works?
thanks
Loic
++