Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.
Is it possible?
I've set the things up, but GUI programs can't access the X server…
in my colinux.conf i have:
I've edited "X0.hosts" to accept clients from 127.0.0.1.
Then in colinux i did:
export DISPLAY 127.0.0.1:0
The settings in your example would not work. There are two fatal errors. Or you are mixed two or more settings.
The "Loopback" is not available with "127.0.0.1" from Linux side. The IP 10.0.2.2 under Linux would be mapped to 127.0.0.1 on Host. The Transmitter is not 127.0.0.1 for SLiRP and pcap-bridge in all cases, so adding 127.0.0.1 to X0.hosts don't help.
You can use SLiRP for Xserver. It is slow, but would work.
For such setup you should use
inside Linux leave eth0 automatic configured via DHCP and export the display like this:
The Xserver must allow connections from localhost (127.0.0.1), or simple add "-ac" to Xming command line.
To use a faster network speed you should use TAP-Win32 and static configured IP address on both ends of that network. For example TAP-Win32 side: 192.168.99.1 and Linux side eth1 with 192.168.99.2. Remember 192.168.99.x should NOT match your default network on real Ethernet adapter!
Configuration for coLinux:
The Xserver must allow connections from 192.168.99.2 or simple add "-ac".
I assume, your network card is named "Local Area Network" and the address on Windows side is like 192.168.0.100
Use your existing Ethernet adapter on host side:
eth0=ndis-bridge,"Local Area Network"
Inside Linux than setup eth0 with an IP address which starts with 192.168.0., for example 192.168.0.2 (or enable DHCP), and use this export:
The Xserver must allow connections from 192.168.0.2 or simple add "-ac".
Thanks for your explanations!
I've tried solutions A) and B).
Since slirp performs quite well on my machine i will stick to A) by now
and avoid having an extra interface in my OS.