Well yes, need "X11Forwarding yes" and "X11DisplayOffset 10" if I wanted to connect to the Z applications. But this freeze too.
A complete howto could be:
-----8<------
Want to connect to another PC using SSH
-> change your root password. If you use an empty password, ssh won't work correctly (if my memory is still efficient).
-> don't forget to specify your username (e.g. ssh username@you_ssh_server_ip)
Want to connect on your Zaurus from another PC using SSH
-> change your root password. If you use an empty password, ssh won't work correctly (if my memory is still efficient).
-> don't forget to specify the username (e.g. ssh root@you_ssh_server_ip)
Want to connect and use X11 applications remotely using SSH
Follow on of the above procedure and use the -X switch (e.g. ssh root@you_ssh_server_ip)
... and more for ssh-keygen and difference between protocol 1, 2...
-----8<------
But this is not the problem.
I tested ssh connexion with big files transfer. No problem. But then I had the idea to do this simultaneously. I mean I used scp from the PC and scp from the Zaurus in order to download and upload data (a kind of X11 data flow simulation). The card then froze.
I don't know if I found the good guilty but apparenlty there's an issue between the kernel driver and the wifi card. The communication freeze for an unknow reason while using high communication in both direction.
As I said, a simple 'cardctl reset' is enough to restart communication. If I don't close the old ssh connexion, the network quickly freeze again. Example: I ping my wifi router without problem, then I switch to the kate frozen window, then I get back to the consol to notice that the network is again frozen.
I will try direct X11 forwarding (I mean without ssh) to see if things work well like this. Perhaps ssh has issues and can freeze the kernel. I never experienced Zaurus network freezes before with pdaXrom (never used ssh).
