Remote X applications

Forum: DSL Embedded
Topic: Remote X applications
started by: enferpuc

Posted by enferpuc on Feb. 08 2006,18:31

Hi all

I'm running DSL-embedded over a WXP. Everything runs well, but when I telnet a remote machine, export the display, and run xclock, all I get is "Error: Can't open display:10.68.8.40:0.0"

Info:
My wxp gets a dhcp IP, which is today 10.68.8.40
My DSL gets a dhcp IP, which is today 10.0.2.15 (and I don't know where it gets it)
The remote machine I want x applications to be shown at my DSL is 10.68.26.5
I can make use of the net when I begin transactions, such as telnet, ftp, http....
Before telnetting 10.68.26.5, I make xhost + at the same xterm.

It's getting on my nerves!!!!!

Thanks for helping

Posted by cbagger01 on Feb. 09 2006,04:01

Please visit the qemu website and their help forums.

They may be able to shed some more light on receiving incoming connections to a virtual PC (in this case, one that is running DSL) and bridging the QEMU simulated networking.

Posted by enferpuc on Feb. 17 2006,11:21

Hi

I tried this command
START qemu\qemu.exe -L qemu/ -enable-audio -localtime -redir tcp:6000::6000 -kernel linux24 -initrd minirt24.gz -hda KNOPPIX/knoppix -hdb qemu/harddisk -append "qemu sb=0x220,5,1,1 frugal quiet modules=hdb"
wich should redirect incomming connections to port 6000 to DSL, but it doesn't work. But, at least, the error I get at the remote server when I launch xclock is:

XIO: Fatal IO error 104 (Connection reset by peer) on X server "myIP:0.0" after 0 request (0 known processed) with 0 events remaining

Don't know what to try next.....

Posted by cbagger01 on Feb. 18 2006,23:46

1) Do you have a firewall or a software firewall program like "Windows Firewall" or "Norton Firewall" or "Zone Alarm? If so, you may need to configure it to allow incoming connections for this port and allow for application qemu.exe

2) Does the redir work for user mode networking? I think DSL uses user mode networking.

3) Last, but not least, there is some security built into the DSL xserver settings regarding tcp connections. Try typing:

beaver /home/dsl/.xserverrc

and edit the startup command line.

Then save and exit.

Finally, restart your x server by "Exit Window Manager" and then type:

startx

after you get a console commandline prompt.

Posted by pr0f3550r on Feb. 19 2006,15:12

The version of Qemu that comes with DSL doesn't support that kind of networking you need.
I am working on this myself and I haven't found the solution. The only feasible solution wuould be aQemu compiled with OpenVPN support, but really you are better off in the Qemu forum or the qemu-devel mailing list

Posted by enferpuc on Feb. 20 2006,08:50

Hi all, and thank you for your advices.

I fixed it. The problem was with the '-nolisten tcp' option passed to the Xserver. After eliminating it, following cbagger01's guideline, everything worked fine, or at least, as I needed to. May be it can also work for pr0f3550r.